From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: plan 9 compose sequences under X
Date: Sun, 2 Jan 2011 15:41:25 -0500 [thread overview]
Message-ID: <AANLkTinwiJKZU4sXm+BjDuNoMCKT2+YfaO_upne4ODk0@mail.gmail.com> (raw)
On Wed, Sep 22, 2010 at 1:56 PM, Russ Cox <rsc@swtch.com> wrote:
> Yes. https://help.ubuntu.com/community/ComposeKey has some
> information on the X11 Compose sequence mechanism. I have
> been meaning to prepare something in p9p to generate a config
> that makes the X11 compose do exactly what p9p does (except
> maybe the alt-X for spelling out Unicode by hex). If you make
> one, please post it. mklatinkbd is probably a good start.
Based on information from Anthony Martin, Tony Lainson, and
Kris Maglione (thanks all!), I have added a -x flag to mklatinkbd,
so that you can get the same compose sequences in GTK and QT
programs that you can in Plan 9 programs. Quoting the updated keyboard(7):
X WINDOWS
Under X Windows, both the Alt key and the ``Multi key'' can
begin a compose sequence in a Plan 9 program.
It is also possible to configure X Windows to use the same
keystroke mappings as the Plan 9 programs. First, generate
an XCompose sequence list by using mklatinkbd:
mklatinkbd -x $PLAN9/lib/keyboard >$HOME/.XCompose
Second, configure a ``Multi key'' by running
xmodmap -e 'keysym Super_L = Multi_key'
(The name `Super_L' typically denotes the Windows key on
recent keyboards.)
Third, set these environment variables so that GTK- and QT-
based programs will use the compose sequences:
export GTK_IM_MODULE=xim
export QT_IM_MODULE=xim
Finally, start a new GTK- or QT-based program:
gnome-terminal &
In that terminal, typing the key sequence `Windows * a'
should be interpreted as the Greek letter `α'.
If using the GNOME Window Manager, put the xmodmap and
export commands into the file $HOME/.gnomerc to run them
automatically at startup.
next reply other threads:[~2011-01-02 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-02 20:41 Russ Cox [this message]
2011-01-02 20:48 ` [9fans] " erik quanstrom
2011-01-03 17:13 ` pmarin
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=AANLkTinwiJKZU4sXm+BjDuNoMCKT2+YfaO_upne4ODk0@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).