From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <33de7d7b-c9b4-6b15-a316-6e3d56c9e5bc@firemail.cc> In-Reply-To: <33de7d7b-c9b4-6b15-a316-6e3d56c9e5bc@firemail.cc> From: Mark van Atten Date: Tue, 18 Dec 2018 04:54:07 +0100 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Enter special characters in acme. Topicbox-Message-UUID: f0a1d9c0-ead9-11e9-9d60-3106f5b1d025 On Tue, Dec 18, 2018 at 3:24 AM Parker Ellertson wrote: > > I'm currently running acme on Debian using plan9port. I've tried using > X11's alt-typing (not sure if that's what it's actually called), and > acme isn't doing squat. I'll probably never have an actual use for it, > but it would be nice to know. Works here (on Arch, but I used the same on FreeBSD and Debian) with this in my .xinitrc: 9 mklatinkbd -x $PLAN9/lib/keyboard >$HOME/.XCompose xmodmap -e 'keycode 108 = Multi_key' # for GNOME and QT programs, add export GTK_IM_MODULE=xim export QT_IM_MODULE=xim # https://unix.stackexchange.com/questions/39547/dead-compose-keys-not-working-in-gtk-apps-since-upgrade/65755#65755 export XMODIFIERS=@im=none Typing ALT, X, four hexadecimal digits works in Acme but not in Firefox for example. The shorthands listed in $PLAN9/lib/keyboard do. Mark.