public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: XFree86 4.3.0 and AltGr
Date: Mon, 29 Dec 2003 23:07:00 -0000	[thread overview]
Message-ID: <3FF0829D.7010502@msu.edu> (raw)
In-Reply-To: <3FEA09E1.2050403@msu.edu>

Can somebody confirm for me whether or not this fixes the AltGr problems 
for them with TweakUI?

Harold

Harold L Hunt II wrote:

> Okay, XFree86-xserv-4.3.0-29 has just been posted.  Please try it and 
> somebody please tell me whether it fixes the problem for them or not.
> 
> Harold
> 
> Harold L Hunt II wrote:
> 
>> I believe I have found just the right amount of magic to fix this once 
>> and for all.  Please stay tuned to test the new release.
>>
>> Harold
>>
>> Philippe Auclair wrote:
>>
>>> Hi,
>>>
>>> Gosh, what an exciting thread about "Proper attribution of patches"!
>>>
>>> Now, to the point... As many Europeans, as Michael Lipp said, "I 
>>> stumbled
>>> over the not-working AltGr" (I have a French keyboard, and a Windows XP
>>> box).
>>>
>>> After various unsuccessful tries with XF86Config, I had a good look 
>>> at the
>>> results of xev. The xev downloaded with Cygwin XFree, and xev on Sun 
>>> Solaris
>>> give similar results: when I press the single key AltGr, xev says:
>>> KeyPress event, serial 18, synthetic NO, window 0xc00001,
>>>     root 0x3a, subw 0x0, time 2826093, (105,60), root:(899,527),
>>>     state 0x10, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
>>>     XLookupString gives 0 characters:  ""
>>>
>>> KeyPress event, serial 18, synthetic NO, window 0xc00001,
>>>     root 0x3a, subw 0x0, time 2826093, (105,60), root:(899,527),
>>>     state 0x14, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), 
>>> same_screen
>>> YES,
>>>     XLookupString gives 0 characters:  ""
>>>
>>> I then tried xmodmap with the following commands:
>>> clear Mod5
>>> keycode 113 = Mode_switch
>>> add Mod3 = Mode_switch
>>>
>>> -> result when pressing AltGr: keycode 37 (Control_L) + keycode 113
>>> (Mode_switch)
>>>
>>> Of course, xterm or emacs don't understand... OK, well is there an 
>>> unused
>>> key at the bottom of the keyboard?
>>> XFree doesn't see the "Windows " key at all, but I have a key which, 
>>> when
>>> pressed in a Windows application, does the same as right click. xev sees
>>> this key as keycode 101. So I feed this into xmodmap:
>>> clear Mod5
>>> keycode 101 = Mode_switch
>>> add Mod3 = Mode_switch
>>> keycode 10 = ampersand 1
>>> keycode 11 = eacute 2 asciitilde
>>> keycode 12 = quotedbl 3 numbersign
>>> keycode 13 = apostrophe 4 braceleft
>>> keycode 14 = parenleft 5 bracketleft
>>> keycode 15 = minus 6 bar
>>> keycode 16 = egrave 7 grave
>>> keycode 17 = underscore 8 backslash
>>> keycode 18 = ccedilla 9 asciicircum
>>> keycode 19 = agrave 0 at
>>> keycode 20 = parenright degree bracketright
>>> keycode 21 = equal plus braceright
>>>
>>> Bingo! xterm and emacs work!  Except I use this odd key instead of 
>>> AltGr,
>>> which I *REALLY* would prefer.
>>>
>>> Hope this helps...
>>>
>>> Philippe Auclair
>>> **********************************************
>>> Institut National de la Recherche Agronomique
>>> Unité Centrale Informatique de Jouy
>>> Domaine de Vilvert, 78352 Jouy-en-Josas CEDEX, France
>>> Philippe.Auclair@jouy.inra.fr
>>> tel +33 1 34 65 26 95, fax +33 1 34 65 24 03
>>> **********************************************
>>>
>>>
>>
> 


  reply	other threads:[~2003-12-29 19:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-24 22:26 Philippe Auclair
2003-12-24 22:30 ` Harold L Hunt II
2003-12-24 22:37 ` Harold L Hunt II
2003-12-25  5:39   ` Harold L Hunt II
2003-12-29 23:07     ` Harold L Hunt II [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-19 13:30 Michael Lipp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FF0829D.7010502@msu.edu \
    --to=huntharo@msu.edu \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).