From: Bertram Scharpf <lists@bertram-scharpf.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Xmodmap with unnamed keycode [solved]
Date: Thu, 20 Jul 2006 01:20:03 +0200 [thread overview]
Message-ID: <20060719232003.GA3821@homer.bertram-scharpf> (raw)
In-Reply-To: <200607182310.31661.benno.schulenberg@gmail.com>
Am Dienstag, 18. Jul 2006, 23:10:31 +0200 schrieb Benno Schulenberg:
> Bertram Scharpf wrote:
> > I would like to map the the character 0x017f, the long s
> > (http://en.wikipedia.org/wiki/Long_s)i, to my X keyboard.
> >
> > $ xmodmap -e 'keycode 39 = s S 0x017f ssharp 0x017f ssharp'
>
> Try this instead:
>
> $ xmodmap -e 'keycode 39 = s S 0x100017f ssharp 0x100017f ssharp'
>
> Why this works, I don't know. :)
Cool. This here seems to work, too:
$ xmodmap -e 'keycode 39 = s S U017f ssharp U017f ssharp'
Obviously there is a difference between UTF codes and X
keycodes. As far as I see, `sacute' is U015b but has a
Xmodmap code of 0x1b6. So both of these yield and
acute-accented s:
$ xmodmap -e 'keycode 39 = s S 0x01b6 ssharp 0x01b6 ssharp'
$ xmodmap -e 'keycode 39 = s S U015b ssharp U015b ssharp'
Setting bit 0x1000000 seems to mean: "take the UTF-16
character".
Thanks a lot.
Bertram
--
Bertram Scharpf
Stuttgart, Deutschland/Germany
http://www.bertram-scharpf.de
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-19 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060718195817.GB2571@homer.bertram-scharpf>
2006-07-18 21:10 ` [gentoo-user] Xmodmap with unnamed keycode Benno Schulenberg
2006-07-19 23:20 ` Bertram Scharpf [this message]
2006-07-20 22:15 ` [gentoo-user] Xmodmap with unnamed keycode [solved] Benno Schulenberg
2006-07-24 19:14 ` Bertram Scharpf
2006-07-24 20:32 ` Benno Schulenberg
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=20060719232003.GA3821@homer.bertram-scharpf \
--to=lists@bertram-scharpf.de \
--cc=gentoo-user@lists.gentoo.org \
/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