unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Input method or help feature needed
Date: Fri, 18 Feb 2011 09:09:44 +0900	[thread overview]
Message-ID: <87lj1ew6d3.fsf@catnip.gol.com> (raw)
In-Reply-To: <m2ipwixolq.fsf@igel.home> (Andreas Schwab's message of "Thu, 17 Feb 2011 23:50:25 +0100")

Andreas Schwab <schwab@linux-m68k.org> writes:

>> Once in a while I want to enter some character that I know exists in
>> Unicode, though I know nothing about where to find it.  Today it was
>> the Turkish i without dot.
>>
>> It is not easy to find how to enter the character you want.
>> Can anyone develop a way to make it easier?
>
> The X11 compose feature actually has pretty easy to remember ways to
> input such characters.  For example, the dotless i can be generated by
> <Multi_key> <i> <.> (<Multi_key> is usually on Shift-RControl).

Isn't that limited to a "common" set of characters in a single locale
though...?

I've tried a lot of these methods before, and the one that generally
seems to work best for obscure characters, and those I'm not used to,
is the "C-x RET * substring TAB" method.

Yeah you need to know or guess part of the name, but the unicode names
are reasonably well chosen, pretty regular, and all you need to know is
_part_ of it; once you can guess that, it's often easy to narrow the
number of choices enough to choose from the completion list...  (often
I'll guess a number of common terms for something, and get a hit after
2-3)

E.g. for dotless-i:  "C-x 8 RET * dotless i TAB" immediately narrows it
down to two choices; just "dotless" gives about 20.

-miles

-- 
`The suburb is an obsolete and contradictory form of human settlement'



  reply	other threads:[~2011-02-18  0:09 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 19:14 Input method or help feature needed Richard Stallman
2011-02-17 19:27 ` Eli Zaretskii
2011-02-17 19:52   ` Stephen Berman
2011-02-17 20:24     ` Harald Hanche-Olsen
2011-02-18 10:53       ` Eli Zaretskii
2011-02-18 15:46         ` Eli Zaretskii
2011-02-18 20:00           ` Ted Zlatanov
2011-02-17 22:05     ` Stefan Monnier
2011-02-18 21:24     ` Richard Stallman
2011-02-19  7:49       ` Eli Zaretskii
2011-02-19  8:01         ` David Kastrup
2011-02-19  8:37           ` Miles Bader
2011-02-20  0:30           ` Richard Stallman
2011-02-20  0:29         ` Richard Stallman
2011-02-20  3:59           ` Eli Zaretskii
2011-02-20 21:01             ` Richard Stallman
2011-02-18 21:24   ` Richard Stallman
2011-02-17 19:31 ` Justin Lilly
2011-02-17 19:41 ` Tassilo Horn
2011-02-18 21:24   ` Richard Stallman
2011-02-19  7:30     ` Eli Zaretskii
2011-02-19  8:18       ` Stephen J. Turnbull
2011-02-19  8:33         ` Miles Bader
2011-03-04  9:10     ` Kevin Rodgers
2011-02-17 20:26 ` Paul Eggert
2011-02-17 22:50 ` Andreas Schwab
2011-02-18  0:09   ` Miles Bader [this message]
2011-02-18  5:13     ` Werner LEMBERG
2011-02-18  8:37     ` tomas
2011-02-18  8:41       ` Miles Bader
2011-02-18 11:27         ` Kenichi Handa
2011-02-20  8:27         ` tomas
2011-02-20 10:41           ` Eli Zaretskii
2011-02-20 11:16             ` David Kastrup
2011-02-20 21:01             ` Richard Stallman
2011-02-20 21:30               ` Eli Zaretskii
2011-02-21  2:53                 ` Stephen J. Turnbull
2011-02-21 22:35                 ` Richard Stallman
2011-02-21  0:59               ` Kenichi Handa
2011-02-21  7:02                 ` Eli Zaretskii
2011-02-21  7:47                   ` Kenichi Handa
2011-02-21  8:25                     ` Miles Bader
2011-02-21  8:29                     ` Eli Zaretskii
2011-02-21 11:14                       ` Kenichi Handa
2011-02-21 12:25                         ` Eli Zaretskii
2011-02-22  0:55                           ` Kenichi Handa
2011-02-22  1:23                             ` Miles Bader
2011-02-21 22:36                         ` Richard Stallman
2011-02-21 22:36                 ` Richard Stallman
2011-02-18  8:43       ` David Kastrup
2011-02-20  8:30         ` tomas
2011-02-20 10:45           ` Eli Zaretskii
2011-02-18 21:25   ` Richard Stallman
2011-02-19  7:52     ` Eli Zaretskii
2011-02-20  0:29       ` Richard Stallman
2011-02-20  7:43         ` James Cloos
2011-02-20 21:01           ` Richard Stallman
2011-02-20 22:45             ` Harald Hanche-Olsen
2011-02-21 22:35               ` Richard Stallman
2011-02-21 22:35               ` Richard Stallman
2011-02-22  6:05                 ` Harald Hanche-Olsen
2011-02-22 20:25                   ` Richard Stallman
2011-02-19 19:26     ` James Cloos
2011-02-20 21:00       ` Richard Stallman
2011-02-20 21:33         ` Drew Adams
2011-02-21 22:36           ` Richard Stallman
2011-02-21 22:51             ` Drew Adams
2011-02-22 20:25               ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2011-02-18 10:39 Андрей Парамонов

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=87lj1ew6d3.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=schwab@linux-m68k.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).