|
View:
New views
15 Messages
—
Rating Filter:
Alert me
|
|
|
Debian packagesHi all,
I've uploaded an early low-package version of my repo, for Janek to get the latest sawfish ;) deb http://www.nanolx.org/apt/ speedwave main deb-src http://www.nanolx.org/apt/ speedwave main when apt complains about the public key, simply grab it from a key sever via the gpg command and apt-key add it and re apt-get update. I'll add more packages later, but that's not of interest for now. Only thing is that I've forgotten to remove the .git dirs from the source tarballs ... so I'll roll out new ones tomorrow, I've already fighted against my tiredness in order to get the sawfish package/ing scripts done. ^_^ Chris |
|
|
Re: Debian packagesAm Samstag, den 24.10.2009, 23:45 +0200 schrieb Christopher Roy
Bratusek: > Hi all, > > I've uploaded an early low-package version of my repo, for Janek to get > the latest sawfish ;) > > deb http://www.nanolx.org/apt/ speedwave main > deb-src http://www.nanolx.org/apt/ speedwave main > > when apt complains about the public key, simply grab it from a key sever > via the gpg command and apt-key add it and re apt-get update. > I'll add more packages later, but that's not of interest for now. > > Only thing is that I've forgotten to remove the .git dirs from the > source tarballs ... so I'll roll out new ones tomorrow, I've already > fighted against my tiredness in order to get the sawfish package/ing > scripts done. ^_^ Done. > Chris |
|
|
Re: Debian packagesChristopher Roy Bratusek said: (by the date of Sat, 24 Oct 2009 23:45:16 +0200)
> I've uploaded an early low-package version of my repo, for Janek to get > the latest sawfish ;) > > deb http://www.nanolx.org/apt/ speedwave main > deb-src http://www.nanolx.org/apt/ speedwave main > > when apt complains about the public key, simply grab it from a key sever > via the gpg command and apt-key add it and re apt-get update. > > I'll add more packages later, but that's not of interest for now. > > Only thing is that I've forgotten to remove the .git dirs from the > source tarballs ... so I'll roll out new ones tomorrow, I've already > fighted against my tiredness in order to get the sawfish package/ing > scripts done. ^_^ This is great! Thanks a lot :) -- Janek Kozicki | |
|
|
Re: Debian packagesChristopher Roy Bratusek said: (by the date of Sun, 25 Oct 2009 06:33:33 +0100)
> > I'll add more packages later, but that's not of interest for now. > Done. I just downloaded deb-src and successfully compiled librep,rep-gtk and sawfish for amd64 :) Thanks a lot. But I have to leave now, so I will start using them tomorrow :) -- Janek Kozicki | |
|
|
Re: Debian packages. Critical bugs before releasing 1.6.0Janek Kozicki said: (by the date of Sun, 25 Oct 2009 07:41:10 +0100)
> I just downloaded deb-src and successfully compiled librep,rep-gtk and > sawfish for amd64 :) Thanks a lot. But I have to leave now, so I will > start using them tomorrow :) OK, I restarted sawfish to start using latest GIT. And after an hour of fiddling I had to revert to 1.5.0. What didn't work: 1) all of my keybindings defined in ~/.sawfish/custom were not there. Ignored, unused, I'm not sure what exactly went wrong. Because the file was not cleaned empty. The bindings are still in it. But in sawfish bindings they are not listed. And they don't work, of course. I notice also that the order of variables is switched in ~/.sawfish/custom, the "window matches" are moved to the top of the file. But apart from that the contents of the file is the same. 2) 9 mouse buttons. I simply could not figure this out. I wanted to configure xbindkeys to send some keycode when I press a mouse button. Then simply change the keybindings in sawfish to use that keycode instead of Button9 and others. But I could not get xbindkeys to generate any useful keycode. It pastes a string in an xterm. No problem. But let's say that I want a Button9 to generate an XF86AudioStop keycode, or an 0x66 keycode. I don't know how. This doesn't work: file ~/.xbindkeysrc "xvkbd -xsendevent -text "\[XF86AudioStop]"" m:0x0 + b:9 This one pastes a string to terminal, when I press Button9: "xvkbd -xsendevent -text "XF86AudioStop"" m:0x0 + b:9 In general I had a plan to use "XK_braille_dot_9" for Button9 "XK_braille_dot_8" for Button8 and so on. And then simply %s/Button9/XK_braille_dot_9/ in ~/.sawfish/custom and have all the Ctrl-Mod4 etc.. combinations working, so C-S-Button9-off2 becomes C-S-XK_braille_dot_9-off2 But I don't see it coming. Also, does anybody know why 'xev' recognizes correctly "Button 9" ? If it has so hidden and complex keycode.... xev: ButtonPress event, serial 33, synthetic NO, window 0x8400001, root 0x2a0, subw 0x0, time 309444666, (162,177), root:(802,627), state 0x10, button 9, same_screen YES So far I'm stuck in 1.5.0 -- Janek Kozicki | |
|
|
Re: Debian packages. Critical bugs before releasing 1.6.0Hi, Janek.
On Tue, 27 Oct 2009 10:23:35 +0100, Janek Kozicki wrote: > What didn't work [in latest GIT version]: > > 1) all of my keybindings defined in ~/.sawfish/custom were not there. > Ignored, unused, I'm not sure what exactly went wrong. Because the > file was not cleaned empty. The bindings are still in it. But in > sawfish bindings they are not listed. And they don't work, of > course. I now installed the latest, but it works as usual. I don't think we have changed in keyboard related part at all since 1.5. Maybe some other process, or zombie instance of sawfish is snatching the key input? > I notice also that the order of variables is switched in > ~/.sawfish/custom, the "window matches" are moved to the top of the > file. But apart from that the contents of the file is the same. Each time you edit options with the configurator, sawfish-config (former sawfish-ui), the order changes, so this is not a problem. # I control my ~/.sawfish/custom with git, but I always filter it with # 'sort', to make the diff meaningful. > 2) 9 mouse buttons. I simply could not figure this out. I wanted to > configure xbindkeys to send some keycode when I press a mouse > button. Then simply change the keybindings in sawfish to use that > keycode instead of Button9 and others. > > But I could not get xbindkeys to generate any useful keycode. It > pastes a string in an xterm. No problem. But let's say that I want > a Button9 to generate an XF86AudioStop keycode, or an 0x66 keycode. > I don't know how. You've installed xvkbd? The page cited from the wiki says "xbindkeys *or* xvkbd", but you need both. Sorry. I'll look for better reference. > file ~/.xbindkeysrc > > "xvkbd -xsendevent -text "\[XF86AudioStop]"" > m:0x0 + b:9 > > This one pastes a string to terminal, when I press Button9: Let me report my trial. I've got synaptic (with synaptics driver), and I tried button 6 & 7. Mine: "xvkbd -xsendevent -text "\[Left]"" m:0x0 + b:6 1. It seems that -xsendevent can be omitted. I couldn't find the difference. 2. I don't know what "m:0x0" means (no modifier?), but it can be omitted. 3. It's unstable. I tried it on emacs. It sometimes works as left, but sometimes reported as "Button 6" 4. The focus goes away when I press button 6. After I focus the window again with window-cycle, then button 6 is sent to the window. Why? 5. After the window is un-focused, my key for raise-lower doesn't recognized. 6. When I bind Alt + Escape (toggle-window-shaded), it works. So it depends on the bound text? I'll search for more on xbindkeys. That's all for now. Regards, Teika (Teika kazura) |
|
|
Re: Debian packages. Critical bugs before releasing 1.6.0Teika Kazura said: (by the date of Tue, 27 Oct 2009 20:45:08 +0900 (JST))
> Hi, Janek. > > On Tue, 27 Oct 2009 10:23:35 +0100, Janek Kozicki wrote: > > What didn't work [in latest GIT version]: > > > > 1) all of my keybindings defined in ~/.sawfish/custom were not there. > > Ignored, unused, I'm not sure what exactly went wrong. Because the > > file was not cleaned empty. The bindings are still in it. But in > > sawfish bindings they are not listed. And they don't work, of > > course. > > I now installed the latest, but it works as usual. I don't think > we have changed in keyboard related part at all since 1.5. Maybe > some other process, or zombie instance of sawfish is snatching the key > input? Perhaps that bug is only affecting me, and I'm acting stupid :) I'll investigate later. Maybe on Friday. > > I notice also that the order of variables is switched in > > ~/.sawfish/custom, the "window matches" are moved to the top of the > > file. But apart from that the contents of the file is the same. > > Each time you edit options with the configurator, sawfish-config > (former sawfish-ui), the order changes, so this is not a problem. > > # I control my ~/.sawfish/custom with git, but I always filter it with > # 'sort', to make the diff meaningful. > > > 2) 9 mouse buttons. I simply could not figure this out. I wanted to > > configure xbindkeys to send some keycode when I press a mouse > > button. Then simply change the keybindings in sawfish to use that > > keycode instead of Button9 and others. > > > > But I could not get xbindkeys to generate any useful keycode. It > > pastes a string in an xterm. No problem. But let's say that I want > > a Button9 to generate an XF86AudioStop keycode, or an 0x66 keycode. > > I don't know how. > > You've installed xvkbd? The page cited from the wiki says "xbindkeys *or* > xvkbd", but you need both. Sorry. I'll look for better reference. > > > file ~/.xbindkeysrc > > > > "xvkbd -xsendevent -text "\[XF86AudioStop]"" > > m:0x0 + b:9 > > > > This one pastes a string to terminal, when I press Button9: > > Let me report my trial. I've got synaptic (with synaptics driver), and > I tried button 6 & 7. > > Mine: > "xvkbd -xsendevent -text "\[Left]"" > m:0x0 + b:6 > > 1. It seems that -xsendevent can be omitted. I couldn't find the difference. > 2. I don't know what "m:0x0" means (no modifier?), but it can be omitted. > 3. It's unstable. I tried it on emacs. It sometimes works as left, but > sometimes reported as "Button 6" > 4. The focus goes away when I press button 6. After I focus the window > again with window-cycle, then button 6 is sent to the window. Why? > 5. After the window is un-focused, my key for raise-lower doesn't > recognized. > 6. When I bind Alt + Escape (toggle-window-shaded), it works. So it > depends on the bound text? > > I'll search for more on xbindkeys. That's all for now. yes, I installed both of them, and I could get a basic functionality, which confirms that it is installed and it works. But what I get was very far from the other's "Buttons N" behaviour. best eragrds -- Janek Kozicki | |
|
|
Re: [IMPORTANT] Support for Buttons 6 7 8 9 dropped -> use evdevHi, Janek.
On Tue, 27 Oct 2009 10:23:35 +0100, Janek Kozicki wrote: > 1) all of my keybindings defined in ~/.sawfish/custom were not there. > Ignored, unused, I'm not sure what exactly went wrong. Because the > file was not cleaned empty. The bindings are still in it. But in > sawfish bindings they are not listed. And they don't work, of > course. What about this problem? Has it gone away? Teika (Teika kazura) |
|
|
Re: Debian packages. Critical bugs before releasing 1.6.0Janek Kozicki said: (by the date of Wed, 28 Oct 2009 07:45:55 +0100)
> > > 1) all of my keybindings defined in ~/.sawfish/custom were not there. > > > > I now installed the latest, but it works as usual. I don't think > > we have changed in keyboard related part at all since 1.5. Maybe > > some other process, or zombie instance of sawfish is snatching the key > > input? > > Perhaps that bug is only affecting me, and I'm acting stupid :) I'll > investigate later. Maybe on Friday. I located the culprit: the first keybinding in a single line in ~/.sawfish/custom referring to Button6,7,8,9 caused all bindings towards the end of line to be ignored. And so I were seeing only 20 out of 200 bindings. > > > 2) 9 mouse buttons. I simply could not figure this out. I wanted to > > > > I'll search for more on xbindkeys. That's all for now. well, no luck with evedev (yet)..... I'm using 1.6 with this patch removed. -- Janek Kozicki | |
|
|
Re: Debian packages. Critical bugs before releasing 1.6.0Am Sat, 14 Nov 2009 08:06:27 +0100
schrieb Janek Kozicki <janek_listy@...>: > Janek Kozicki said: (by the date of Wed, 28 Oct 2009 07:45:55 > +0100) > > > > > 1) all of my keybindings defined in ~/.sawfish/custom were not > > > > there. > > > > > > I now installed the latest, but it works as usual. I don't think > > > we have changed in keyboard related part at all since 1.5. Maybe > > > some other process, or zombie instance of sawfish is snatching > > > the key input? > > > > Perhaps that bug is only affecting me, and I'm acting stupid :) I'll > > investigate later. Maybe on Friday. > > I located the culprit: the first keybinding in a single line in > ~/.sawfish/custom referring to Button6,7,8,9 caused all bindings > towards the end of line to be ignored. And so I were seeing only 20 > out of 200 bindings. Fuck. This needs to be fixed, before release. (Even if mouse branch is reverted, as say you accidently used ^ or ° for a binding instead of 1 (one of the former two is not a valid key for bindings) the result is the same, sawfish should be more tolerant here and just remove the wrong one from config or atleast just ignore it) > > > > 2) 9 mouse buttons. I simply could not figure this out. I > > > > wanted to > > > > > > I'll search for more on xbindkeys. That's all for now. > > well, no luck with evedev (yet)..... I'm using 1.6 with this patch > removed. > |
|
|
Re: Debian packages. Critical bugs before releasing 1.6.0Christopher Roy Bratusek said: (by the date of Sat, 14 Nov 2009 08:09:25 +0100)
> Am Sat, 14 Nov 2009 08:06:27 +0100 > schrieb Janek Kozicki <janek_listy@...>: > > > Janek Kozicki said: (by the date of Wed, 28 Oct 2009 07:45:55 > > +0100) > > > > > > > 1) all of my keybindings defined in ~/.sawfish/custom were not > > > > > there. > > > > > > > > I now installed the latest, but it works as usual. I don't think > > > > we have changed in keyboard related part at all since 1.5. Maybe > > > > some other process, or zombie instance of sawfish is snatching > > > > the key input? > > > > > > Perhaps that bug is only affecting me, and I'm acting stupid :) I'll > > > investigate later. Maybe on Friday. > > > > I located the culprit: the first keybinding in a single line in > > ~/.sawfish/custom referring to Button6,7,8,9 caused all bindings > > towards the end of line to be ignored. And so I were seeing only 20 > > out of 200 bindings. > > Fuck. This needs to be fixed, before release. (Even if mouse branch is > reverted, as say you accidently used ^ or ° for a binding instead of 1 > (one of the former two is not a valid key for bindings) the result is > the same, sawfish should be more tolerant here and just remove the > wrong one from config or atleast just ignore it) for start we could just give the user some warning "Unrecognised keybinding, ignoring all other keybindings, edit your ~/.sawfish/custom to fix this (and remember to backup it first)". So that he knows that something is wrong, this will fix that stupid feeling "wtf, where are all my bindings?". -- Janek Kozicki | |
|
|
Re: Debian packages. Critical bugs before releasing 1.6.0Am Sat, 14 Nov 2009 08:27:11 +0100
schrieb Janek Kozicki <janek_listy@...>: > Christopher Roy Bratusek said: (by the date of Sat, 14 Nov 2009 > 08:09:25 +0100) > > > Am Sat, 14 Nov 2009 08:06:27 +0100 > > schrieb Janek Kozicki <janek_listy@...>: > > > > > Janek Kozicki said: (by the date of Wed, 28 Oct 2009 07:45:55 > > > +0100) > > > > > > > > > 1) all of my keybindings defined in ~/.sawfish/custom were > > > > > > not there. > > > > > > > > > > I now installed the latest, but it works as usual. I don't > > > > > think we have changed in keyboard related part at all since > > > > > 1.5. Maybe some other process, or zombie instance of sawfish > > > > > is snatching the key input? > > > > > > > > Perhaps that bug is only affecting me, and I'm acting stupid :) > > > > I'll investigate later. Maybe on Friday. > > > > > > I located the culprit: the first keybinding in a single line in > > > ~/.sawfish/custom referring to Button6,7,8,9 caused all bindings > > > towards the end of line to be ignored. And so I were seeing only > > > 20 out of 200 bindings. > > > > Fuck. This needs to be fixed, before release. (Even if mouse branch > > is reverted, as say you accidently used ^ or ° for a binding > > instead of 1 (one of the former two is not a valid key for > > bindings) the result is the same, sawfish should be more tolerant > > here and just remove the wrong one from config or atleast just > > ignore it) > > > for start we could just give the user some warning "Unrecognised > keybinding, ignoring all other keybindings, edit your > ~/.sawfish/custom to fix this (and remember to backup it first)". So > that he knows that something is wrong, this will fix that stupid > feeling "wtf, where are all my bindings?". > Perhaps bind_keys from src/keys.c just needs to throw the bad binding from the list? Chris |
|
|
Re: Debian packages. Critical bugs before releasing 1.6.0Christopher Roy Bratusek said: (by the date of Sat, 14 Nov 2009 09:54:17 +0100)
> Perhaps bind_keys from src/keys.c just needs to throw the bad binding > from the list? I'd prefer that ~/.sawfish/custom remains unchanged. If I lost my 100+ bindings for Button6,7,8,9 after upgrade and I didn't have a backup I'd get mad. (but I have backups, of course, this night I've spent 5h playing with raid5 config and rsnapshot and hardlinks ;) So: - ignore binding: yes - Don't change ~/.sawfish/custom. Or make a backup file if some bindings were ignored, and the file is saved. -- Janek Kozicki | |
|
|
Re: Debian packages. Critical bugs before releasing 1.6.0Am Sat, 14 Nov 2009 11:15:00 +0100
schrieb Janek Kozicki <janek_listy@...>: > Christopher Roy Bratusek said: (by the date of Sat, 14 Nov 2009 > 09:54:17 +0100) > > > Perhaps bind_keys from src/keys.c just needs to throw the bad > > binding from the list? > > I'd prefer that ~/.sawfish/custom remains unchanged. If I lost my > 100+ bindings for Button6,7,8,9 after upgrade and I didn't have a > backup I'd get mad. (but I have backups, of course, this night I've > spent 5h playing with raid5 config and rsnapshot and hardlinks ;) > I meant internally. > So: > > - ignore binding: yes > > - Don't change ~/.sawfish/custom. Or make a backup file if some > bindings were ignored, and the file is saved. > |
|
|
Re: Debian packages. Critical bugs before releasing 1.6.0On Sat, 14 Nov 2009 08:09:25 +0100, Christopher Roy Bratusek wrote:
> Am Sat, 14 Nov 2009 08:06:27 +0100 > schrieb Janek Kozicki <janek_listy@...>: >> I located the culprit: the first keybinding in a single line in >> ~/.sawfish/custom referring to Button6,7,8,9 caused all bindings >> towards the end of line to be ignored. And so I were seeing only 20 >> out of 200 bindings. > > F[***]. This needs to be fixed, before release. If you try to define bad key from the configurator, you can't. A window pops up, for example, saying: While changing title-keymap: bad-event-desc: RET-Move So it must be not so difficult. Regards, Teika (Teika kazura) |
| Free embeddable forum powered by Nabble | Forum Help |