Re: FVWM: FVWM don't still read my xmodmap's setting,why?

From: Dan Espen <dane_at_mk.telcordia.com>
Date: Sat, 26 Jun 2004 14:03:59 -0400

lee <learnman_at_21cn.com> writes:
> But FVWM still can not read my xmodmap , like the question why FVWM
> can read the command line "xmodmop -e 'keycode 222 = XF86Poweroff'" and
> works correctly, but it can not read my setting in .Xmodmap regardless
> of i append "xmodmap $HOME/.xmodmap" or not .
>
> I've used another method just set these into my .fvwm2rc file, like
> this:
> ...
> InitFunction
> + I Exec exec xmodmap $HOME/.xmodmap
> ...
> The problem still exists

That should be:

AddToFunc InitFunction
+ I Exec exec xmodmap ~/.xmodmap

On my system, the .xmodmap file should contain:

keycode 222 = 86_Poweroff

If I use the "XF", I get:

home> xmodmap -e 'keycode 222 = XF86Poweroff'
xmodmap: commandline:0: bad keysym name 'XF86Poweroff' in keysym list
xmodmap: 1 error encountered, aborting.


-- 
Dan Espen                           E-mail: dane_at_mk.telcordia.com
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sat Jun 26 2004 - 14:53:37 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:56 BST