From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Acme and unicode
Date: Wed, 14 May 2008 16:50:12 -0400 [thread overview]
Message-ID: <20080514205423.C29241E8C51@holo.morphisms.net> (raw)
In-Reply-To: <b4ff0246eb5be50f701a3892475d0e5b@9srv.net>
> keyboard(7) (keyboard(6) on plan 9). lots of shortcuts for
> specific things, but alt+x+1234 should produce glyphs.
> see also $PLAN9/lib/keyboard.
It is perhaps worth pointing out that in Plan 9
(and in Plan 9 from User Space), Alt is just a
key like any other, not a modifier like Shift:
you don't have to hold it down through the entire
sequence. It is also perhaps worth pointing out
that the letter must be a capital X.
So you can type Alt, X, 2, 6, 3, a to get ☺.
Russ
next prev parent reply other threads:[~2008-05-14 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 14:44 hugo rivera
2008-05-14 14:49 ` a
2008-05-14 20:50 ` Russ Cox [this message]
2008-05-14 23:00 ` John Stalker
2008-05-15 9:40 ` hugo rivera
2008-05-14 14:52 ` andrey mirtchovski
2008-05-14 14:53 ` Skip Tavakkolian
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=20080514205423.C29241E8C51@holo.morphisms.net \
--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).