all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: herring@lanl.gov
Cc: Juri Linkov <juri@jurta.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Feature needed
Date: Tue, 15 Jun 2010 05:35:56 -0400	[thread overview]
Message-ID: <m3mxuw63jf.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <49520.130.55.132.126.1276531995.squirrel@webmail.lanl.gov> (Davis Herring's message of "Mon, 14 Jun 2010 09:13:15 -0700 (PDT)")

>>>>> "DH" == Davis Herring <herring@lanl.gov> writes:

>> `C-u C-x =' displays this information.  For instance,
>> 
>> character: Ä (196, #o304, #xc4)
>> to input: type "\"{A}" or "\"A" with TeX
>> 
>> where the name of the input method has a link to its description.

DH> Doesn't it only check the current input method?

Indeed.  And even then it does't always report.  [See below.]

Checking every input method might be too ram or i/o intensive for all
users, but would make a reasonable option.

Or, given that the C-u C-x = output already has a link to customize what
Character code properties to show, it could have one to customize which
input methods to check, with the default being 'current.

Another possibility might be to have a script -> input mapping and to
use that to show a useful input method if the current one cannot input
the character in question.

I just tried out the name »παν語« (cf http://www.pango.org/), and even
with the japanese input method selected -- which I used to input the go --
the C-u C-x = output for 語 did not explain how to enter it.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6



  reply	other threads:[~2010-06-15  9:35 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3mxuw63jf.fsf@carbon.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=emacs-devel@gnu.org \
    --cc=herring@lanl.gov \
    --cc=juri@jurta.org \
    --cc=rms@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.