On Fri, 16 Dec 2005 13:14:34 +0200 Bradley Reed <[EMAIL PROTECTED]> wrote:
> This may be due to my stupidity, but I decided to try the new > init/start/stop scripting capabilities of e16.8 and came upon a > glitch. > > I had moved the following into my e16.8 init script > > # New Laptop's volume keys > /usr/X11R6/bin/xmodmap -e 'keycode 176 = XF86AudioRaiseVolume' > /usr/X11R6/bin/xmodmap -e 'keycode 174 = XF86AudioLowerVolume' > /usr/X11R6/bin/xmodmap -e 'keycode 160 = XF86AudioMute' > > instead of where they had been previously > (.xsession/.xmodmap/.xprofile .. I forget) Just thought I'd mention I wasn't asking for a fix, I moved the above commands back to .xsession and all is well. I just wanted to mention my experience because it was unexpected. I really expected if a key was defined, and a keybinding was assigned to it, that the keybinding would work. This wasn't the case. xev showed the key was working, e16 just wasn't doing anything with it. By the way, thanks for implementing this Init/Start/Stop scripts into e16. It is a really nice feature! Brad ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
