Re: Serious problems with writing @

[Nicola Pero]

> > > Yes, I have downloaded it and I don't know if it is really what I need.
> > > The problem comes from the key "alt right" which display "*". How could
> > > I avoiding this issue with KeyPrefs.app ?
> >    
> > the app is just a front-end to the gnustep modifier configuration system,
> > which is explained in
> >    
> > http://www.gnustep.org/resources/documentation/gnustep-gui_6.html#SEC43
> 
> >From that File:
> COMMAND is used to enter key equivalents (keyboard shortcuts for menus or 
> buttons); for example, usually 'Quit' on the main menu of an application is 
> bound to 'q', so
>      you may usually quit a GNUstep application by pressing Command - q. 
> 
> I checked my settings with KeyPrefs.app and they are set to the default 
> values but menu shortcuts only work when pressing ALT + CONTROL +
> shortcut simultaneously... I'm just curious whether that's a flaw of
> gstep or an error in my x11 configuration. 

which ALT and CONTROL keys ? left or right ... ?

Anyway - here are some things you can do to figure out what's happing - 

- open an X terminal, and start `xev' from there

- a little white window opens.  go into the window, and press the key 
  you want to be bound to Command (in my case, the left Alt).

  in the xterm you should see something like -

KeyPress event, serial 21, synthetic NO, window 0x2c00001,
    root 0x26, subw 0x0, time 2422979481, (140,142), root:(315,339),
    state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 characters:  ""

KeyRelease event, serial 21, synthetic NO, window 0x2c00001,
    root 0x26, subw 0x0, time 2422979580, (140,142), root:(315,339),
    state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 characters:  ""

this (in my case) means that the left Alt is called `Alt_L' on my system.  
On your system, it will probably display something else (since you say the
default configuration doesn't work).  Tell gnustep you want that key to be
your Command key by typing at a shell prompt

defaults write NSGlobalDomain GSFirstCommandKey Alt_L

(replacing Alt_L with what you read as the keysym from xev's output).  You
can use xev to study what your different keys are called on your X
configuration.

To check how gnustep is interpreting your keys, you can run the GSTest
application (from examples/gui/GSTest), then select KeyboardInput, then
examine what happens when you type the various keys inside the
KeyboardInput window.

Once you have determined what is the problem - which keys are mapped wrong
and/or why the default configuration doesn't work etc, you can modify the
mapping by using the defaults system as explained in the text.

Finally, let us know the results of your investigations :-)