unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Unicode progress tooltip?
Date: Sun, 11 Oct 2020 19:45:13 +0300	[thread overview]
Message-ID: <83eem44spy.fsf@gnu.org> (raw)
In-Reply-To: <CANc-5Uyxm3BbGTJ63_F00BmH9UHPC1jpswbbb06z8_XH=77Nfw@mail.gmail.com> (message from Skip Montanaro on Sun, 11 Oct 2020 11:20:48 -0500)

> From: Skip Montanaro <skip.montanaro@gmail.com>
> Date: Sun, 11 Oct 2020 11:20:48 -0500
> 
> I have a US layout keyboard. I occasionally need to type non-ASCII stuff
> like ¾, ₤ or é. I've now memorized a few Compose key sequences (environment
> is Ubuntu 20.04), but golly gee, there are a lot of them! I noticed that
> when I mash down on the Compose key a little tooltip pops up
> 
> [image: Screenshot from 2020-10-11 10-59-29.png]
> 
> and is extended as more keys are pressed. Once a complete sequence is
> entered, the appropriate glyph is rendered and the tooltip dismissed. This
> is very nice.
> 
> Still, I wonder... Is there a way to get Emacs to display all the
> possibilities for the next key and the resulting glyph? This would be sort
> of like the long press over a key on my Android phone which brings up a
> pop-up menu showing the various related characters you can select. For
> example, after entering Compose L, it appears the "next set" only contains
> eight characters (according to my computer's Compose file). Is there some
> package which can parse the Compose file and present the next characters
> and potentially the final possible glyphs? I poked around in the package
> list on my Emacs install (v 26.3). None of the packages matching the search
> string "unicode" seemed like what I was looking for.

Try

  C-u C-\ TeX RET

and then

  C-h C-\ RET

to see the combinations.



  reply	other threads:[~2020-10-11 16:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11 16:20 Unicode progress tooltip? Skip Montanaro
2020-10-11 16:45 ` Eli Zaretskii [this message]
2020-10-12  4:10   ` Pankaj Jangid
2020-10-11 16:52 ` Pankaj Jangid
2020-10-11 17:33   ` Stefan Kangas
2020-10-12  4:24     ` Pankaj Jangid
2020-10-12 10:13   ` Robert Pluim
2020-10-13  5:38     ` Jean Louis
2020-10-13 14:17     ` Stefan Monnier
2020-10-11 19:24 ` Skip Montanaro
2020-10-11 19:58   ` Drew Adams
2020-10-13 11:38   ` Skip Montanaro

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=83eem44spy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).