unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Juri Linkov <juri@jurta.org>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: find-composition still depends on the composition property
Date: Mon, 20 Oct 2008 15:46:37 +0900	[thread overview]
Message-ID: <E1KroXF-0005mK-07@etlken.m17n.org> (raw)
In-Reply-To: <87tzbh7kd9.fsf@jurta.org> (message from Juri Linkov on Mon, 20 Oct 2008 02:15:17 +0300)

In article <87tzbh7kd9.fsf@jurta.org>, Juri Linkov <juri@jurta.org> writes:

> What do you think about displaying the Unicode information of the
> combining character too?

> Currently there is no easy way to display the information (name, category)
> about the combining character because the user can't put point on the
> combining character and type `C-u C-x ='.

When you type C-u C-x = on a composed characters, Emacs
displays how it is composed.  For instance, when a buffer
contains the sequence "a" "U+300" "U+316" composed into one
glyph, and you type C-u C-x = on it, Emacs shows something
like this information.

[...]
Composed with the following character(s) "̖́" using this font:
                                         ^^^^
  xft:-Misc-Fixed-normal-normal-normal-*-20-*-*-*-c-*-iso10646-1
by these glyphs:
[...]

As each character ocupies one column in the part "̖́", you can
easily put cursor on any of a character and type C-u C-x =.

Isn't it good enough?

---
Kenichi Handa
handa@ni.aist.go.jp




  reply	other threads:[~2008-10-20  6:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29 13:46 find-composition still depends on the composition property Juanma Barranquero
2008-09-05  1:24 ` Kenichi Handa
2008-10-19 23:15   ` Juri Linkov
2008-10-20  6:46     ` Kenichi Handa [this message]
2008-10-21 23:46       ` Juri Linkov
2008-10-22  1:17         ` Kenichi Handa
2008-10-22  4:25           ` Eli Zaretskii
2008-10-22  5:43             ` Kenichi Handa
2008-10-22  5:29           ` Kenichi Handa
2008-10-22 19:35             ` Eli Zaretskii
2008-10-23  1:18               ` Kenichi Handa
2008-10-23 23:44                 ` describe-categories (was: find-composition still depends on the composition property) Juri Linkov
2008-10-25  1:37                   ` Kenichi Handa
2008-10-25  8:33                     ` Eli Zaretskii
2008-10-23 23:48                 ` Word boundary " Juri Linkov
2008-10-25 18:03                   ` Eli Zaretskii
2008-10-26 13:36                     ` Kenichi Handa
2008-10-26 19:32                       ` Eli Zaretskii
2008-10-27  0:17                         ` Word boundary Miles Bader
2008-10-27  0:27                           ` Kenichi Handa
2008-10-27  4:12                             ` Eli Zaretskii
2008-10-27  5:16                             ` Miles Bader
2008-10-31  5:50                               ` Kenichi Handa
2008-10-26  8:15                   ` Word boundary (was: find-composition still depends on the composition property) Kenichi Handa

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=E1KroXF-0005mK-07@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=lekktu@gmail.com \
    /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).