Re: Xwindows keymap weirdness

2020-06-01 Thread Marc Espie
On Mon, Jun 01, 2020 at 03:37:45PM -0600, Anthony J. Bentley wrote: > Marc Espie writes: > > > To setup the right alt key as compose, you can either: > > > > > > - run 'setxkbmap -option compose:ralt' somewhere in your session > > > startup script > > > > > > - create

Re: Xwindows keymap weirdness

2020-06-01 Thread Anthony J. Bentley
Marc Espie writes: > > To setup the right alt key as compose, you can either: > > > > - run 'setxkbmap -option compose:ralt' somewhere in your session > > startup script > > > > - create /etc/X11/xorg.conf.d/90-keyboard.conf containing > > > > --- Cut --- > > Section "InputClass" > >

Re: Xwindows keymap weirdness

2020-06-01 Thread Marc Espie
On Mon, Jun 01, 2020 at 03:46:09PM +0200, Matthieu Herrb wrote: > On Mon, Jun 01, 2020 at 03:28:52PM +0200, Stéphane Aulery wrote: > > Hello, > > > > Le 01/06/2020 14:55, Matthieu Herrb a écrit : > > > > > > > > > > > (I have just tried with a test user with nothing configured besides > > > >

Re: Xwindows keymap weirdness

2020-06-01 Thread Stuart Henderson
On 2020/06/01 15:56, Stéphane Aulery wrote: > Le 01/06/2020 15:46, Matthieu Herrb a écrit : > > On Mon, Jun 01, 2020 at 03:28:52PM +0200, Stéphane Aulery wrote: > > > Le 01/06/2020 14:55, Matthieu Herrb a écrit : > > > > > > > > > > > > > > (I have just tried with a test user with nothing

Re: Xwindows keymap weirdness

2020-06-01 Thread Christian Weisgerber
Marc Espie: > If I type 'c > > I get a ç in programs like firefox or chrome, BUT I get > ć in xterm ? > > why are things different ? which program is right ? GTK comes with its own compose rules that are occasionally different from the default X11 ones. Personally, I disable GTK's compose

Re: Xwindows keymap weirdness

2020-06-01 Thread Stéphane Aulery
Le 01/06/2020 15:46, Matthieu Herrb a écrit : On Mon, Jun 01, 2020 at 03:28:52PM +0200, Stéphane Aulery wrote: Le 01/06/2020 14:55, Matthieu Herrb a écrit : > > > > > (I have just tried with a test user with nothing configured besides > > LC_CTYPE=en_US.UTF-8, without which xterm/vim doesn't

Re: Xwindows keymap weirdness

2020-06-01 Thread Matthieu Herrb
On Mon, Jun 01, 2020 at 03:28:52PM +0200, Stéphane Aulery wrote: > Hello, > > Le 01/06/2020 14:55, Matthieu Herrb a écrit : > > > > > > > > (I have just tried with a test user with nothing configured besides > > > LC_CTYPE=en_US.UTF-8, without which xterm/vim doesn't show proper > > >

Re: Xwindows keymap weirdness

2020-06-01 Thread Stéphane Aulery
Hello, Le 01/06/2020 14:55, Matthieu Herrb a écrit : (I have just tried with a test user with nothing configured besides LC_CTYPE=en_US.UTF-8, without which xterm/vim doesn't show proper characters) I'm using a real US keyboard with AltGr or the Menu Key (depending on the actual keyboard)

Re: Xwindows keymap weirdness

2020-06-01 Thread Matthieu Herrb
On Mon, Jun 01, 2020 at 02:16:16PM +0200, Marc Espie wrote: > I occasionnally use setxkbmap 'us(intl)' in order to have diacritics > as dead keys. > > I have LC_CTYPE=en_US.UTF-8 > > If I type 'c > > I get a ç in programs like firefox or chrome, BUT I get > ć in xterm ? > > why are things

Xwindows keymap weirdness

2020-06-01 Thread Marc Espie
I occasionnally use setxkbmap 'us(intl)' in order to have diacritics as dead keys. I have LC_CTYPE=en_US.UTF-8 If I type 'c I get a ç in programs like firefox or chrome, BUT I get ć in xterm ? why are things different ? which program is right ? (I have just tried with a test user with