From: Miles Bader <miles@gnu.org>
To: rms@gnu.org
Cc: juri@jurta.org, "Stephen J. Turnbull" <stephen@xemacs.org>,
cloos@jhcloos.com, emacs-devel@gnu.org
Subject: Re: Feature needed
Date: Thu, 17 Jun 2010 17:49:56 +0900 [thread overview]
Message-ID: <buoljaedowb.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <E1OPA2J-0001nx-JF@fencepost.gnu.org> (Richard Stallman's message of "Thu, 17 Jun 2010 04:01:19 -0400")
Richard Stallman <rms@gnu.org> writes:
> I saw a character I did not know about, and I wanted to know how to
> input it in the future. Yes, I could have copied it to a file and
> saved the file, so as to copy it from there. But I wanted to know how
> to insert it cleanly.
>
> Remembering a unicode code point is not a good solution, since that
> would be hard to remember.
One very convenient way to enter unusual characters these days is
via the unicode character _name_, via "C-x 8 RET". The resulting
prompt supports completion (including non-initial completion by
using "* something TAB"), it's reasonably easy to find the name even
if you only know part of it.
-Miles
--
Kilt, n. A costume sometimes worn by Scotchmen [sic] in America and Americans
in Scotland.
next prev parent reply other threads:[~2010-06-17 8:49 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 8:13 Feature needed Richard Stallman
2010-06-14 15:35 ` Juri Linkov
2010-06-14 16:13 ` Davis Herring
2010-06-15 9:35 ` James Cloos
2010-06-15 10:22 ` Miles Bader
2010-06-15 12:28 ` Geoff Gole
2010-06-16 10:57 ` Richard Stallman
2010-06-16 14:25 ` Geoff Gole
2010-06-17 10:46 ` Richard Stallman
2010-06-15 12:45 ` James Cloos
2010-06-16 3:22 ` Stephen J. Turnbull
2010-06-16 6:14 ` Daniel Clemente
2010-06-16 12:01 ` Stephen J. Turnbull
2010-06-17 4:24 ` Kevin Rodgers
2010-06-17 10:45 ` Richard Stallman
2010-06-16 6:50 ` Miles Bader
2010-06-16 11:43 ` James Cloos
2010-06-18 6:51 ` Stephen J. Turnbull
2010-06-17 8:01 ` Richard Stallman
2010-06-18 1:47 ` Miles Bader
2010-06-18 12:20 ` Andreas Schwab
2010-06-17 8:01 ` Richard Stallman
2010-06-17 8:49 ` Miles Bader [this message]
2010-06-17 19:26 ` Richard Stallman
2010-06-18 7:01 ` Stephen J. Turnbull
2010-06-18 8:37 ` Miles Bader
2010-06-18 23:59 ` Richard Stallman
2010-06-18 23:59 ` Another input method feature needed Richard Stallman
2010-06-19 8:47 ` Juri Linkov
2010-06-19 11:13 ` Štěpán Němec
2010-06-19 14:08 ` Juri Linkov
2010-06-19 18:16 ` Štěpán Němec
2010-06-19 20:48 ` Juri Linkov
2010-06-20 4:08 ` Kenichi Handa
2010-06-20 21:28 ` Juri Linkov
2010-06-20 17:01 ` Stephen J. Turnbull
2010-06-20 21:34 ` Juri Linkov
2010-06-25 12:08 ` Štěpán Němec
2010-06-28 21:19 ` Juri Linkov
2010-07-01 0:05 ` Stefan Monnier
2010-07-02 20:52 ` Juri Linkov
2010-06-19 23:37 ` Richard Stallman
2010-06-20 21:42 ` Juri Linkov
2010-06-21 12:09 ` Richard Stallman
2010-06-21 12:43 ` Andreas Schwab
2010-06-19 15:18 ` Stephen J. Turnbull
2010-06-19 16:03 ` Miles Bader
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=buoljaedowb.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=cloos@jhcloos.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=rms@gnu.org \
--cc=stephen@xemacs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).