all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 3568@debbugs.gnu.org
Subject: bug#3568: 23.0.94; no doc for character composition
Date: Wed, 27 Apr 2016 12:42:56 -0700 (PDT)	[thread overview]
Message-ID: <623906f5-d8d6-416b-b435-7f3b0f44944a@default> (raw)
In-Reply-To: <87potadfe9.fsf@gnus.org>

> > I can find no doc at all regarding character composition, beyond the
> > cursory explanation given in the Emacs manual, node Input Methods.
> >
> > In particular, there is nothing in the Elisp manual about it. No
> > documentation of functions such as `compose-region' and
> > `compose-chars'.
> >
> > And there is no usage commentary in `composite.el'.
> >
> > How does one compose characters using Emacs Lisp? If characters have
> > been composed, how do you decompose them? Are there any caveats to be
> > aware of? Users will have such questions.
> 
> `compose-region' has a very long doc string...  And it seems to have
> been added to after you wrote this bug report.  Does it answer your
> questions now?

No.  `compose-region' already had that doc string when the bug was
reported.  That doc string has been around since at least Emacs 22.

I would expect some conceptual explanation of character composition
in the Elisp manual.  Including how to decompose composed chars etc.
What the bug report mentions.  I don't think that a doc string for
one command covers this topic.





  reply	other threads:[~2016-04-27 19:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 23:17 bug#3568: 23.0.94; no doc for character composition Drew Adams
2016-04-27 19:23 ` Lars Ingebrigtsen
2016-04-27 19:42   ` Drew Adams [this message]
2016-04-27 20:11     ` Eli Zaretskii
     [not found]   ` <<623906f5-d8d6-416b-b435-7f3b0f44944a@default>
     [not found]     ` <<83mvoeyfpx.fsf@gnu.org>
2016-04-27 21:18       ` Drew Adams
2016-04-28  5:07         ` Eli Zaretskii

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=623906f5-d8d6-416b-b435-7f3b0f44944a@default \
    --to=drew.adams@oracle.com \
    --cc=3568@debbugs.gnu.org \
    --cc=larsi@gnus.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.