Re: FVWM: Binding keys with NoSymbol key name
Le Sat, 14 Jul 2007 06:52:37 +0100, Leo [EMAIL PROTECTED] a écrit : On 2007-07-11 22:58 +0100, Gautam Iyer wrote: I had the same problem a few days ago. You can use xmodmap to remap as follows. First find a keysym name to assign to these keys. Try doing grep -i audio /usr/share/X11/XKeysymDB [...] on fvwm startup. Finally, I have in my fvwm bindings key XF86AudioMute A N Exec exec amixer -q set Master toggle key XF86AudioRaiseVolumeA N Exec exec amixer -q set Master 2+ key XF86AudioLowerVolumeA N Exec exec amixer -q set Master 2- Many thanks. This greatly improves productivity ;) The only thing I am unhappy about is that the above just increases / decreases the volume, and gives you no confirmation or indication of what the volume is. I wouldn't mind a volume slider, like on my TV. Xosd has a nice volume slider, but that involves me writing a script that gets the current volume and feeds it to xosd. Should you, or anyone else on the list, know of a script / application that was designed for this purpose, let me know :) This will be nice but I don't know any program that does that. You can combine a call to xmessage with amixer: amixer sget Master | xmessage -timeout 10 -file - but this will be very verbose. You have to sort it with grep in the middle. amixer sget Master | grep Capture | xmessage -timeout 3 -file - and add further filtering with sed if needed. Dominique GI -- Dominique Michel -- N.B.: Tous les emails que je reçois sont filtrés par spamassassin avant de me parvenir.
Re: FVWM: Binding keys with NoSymbol key name
Personally I mainly use Amarok (from KDE) as a music player and allow it to create some 'global short cuts' which then also work enabling Start/Stop, Pause, Forward, Backward, Volume Up/Down, Trackrating etc. On 7/14/07, Dominique Michel [EMAIL PROTECTED] wrote: Le Sat, 14 Jul 2007 06:52:37 +0100, Leo [EMAIL PROTECTED] a écrit : On 2007-07-11 22:58 +0100, Gautam Iyer wrote: I had the same problem a few days ago. You can use xmodmap to remap as follows. First find a keysym name to assign to these keys. Try doing grep -i audio /usr/share/X11/XKeysymDB [...] on fvwm startup. Finally, I have in my fvwm bindings key XF86AudioMute A N Exec exec amixer -q set Master toggle key XF86AudioRaiseVolumeA N Exec exec amixer -q set Master 2+ key XF86AudioLowerVolumeA N Exec exec amixer -q set Master 2- Many thanks. This greatly improves productivity ;) The only thing I am unhappy about is that the above just increases / decreases the volume, and gives you no confirmation or indication of what the volume is. I wouldn't mind a volume slider, like on my TV. Xosd has a nice volume slider, but that involves me writing a script that gets the current volume and feeds it to xosd. Should you, or anyone else on the list, know of a script / application that was designed for this purpose, let me know :) This will be nice but I don't know any program that does that. You can combine a call to xmessage with amixer: amixer sget Master | xmessage -timeout 10 -file - but this will be very verbose. You have to sort it with grep in the middle. amixer sget Master | grep Capture | xmessage -timeout 3 -file - and add further filtering with sed if needed. Dominique GI -- Dominique Michel -- N.B.: Tous les emails que je reçois sont filtrés par spamassassin avant de me parvenir. -- Met vriendelijke groeten / With kind regards Hans Voss --- * Senior Consultant Open Source, Networking and Security * google talk enabled * General Open Sourcerer.
Re: FVWM: FVWM Environment variables
[ Grumbles about stupid shed-painting... ] On 13/07/07, Ryan Daly [EMAIL PROTECTED] wrote: On Thu, 2007-07-12 at 20:43 -0400, Gautam Iyer wrote: Erm. This is a feature of su and not fvwm. I think su clears most variables before starting a root shell. For instance if I do env ASDF=hello su - on my system, then root still can not see the environment ASDF. You might be able to do some pam magic to disable this... I AM NOT DOING AN 'su' TO ROOT. I am logging in from XDM as root and not seeing the environment that I'm specifying in my configuration. And how might you be starting FVWM? Are you relying on the use of ~/.xsession? Is FVWM even being told where to look for the config file? (Assuming it's not already /root/.fvwm/config, or one of the other seven different varieties the man page lists as being part of its search procedure.) -- Thomas Adam
