From: "Drew Adams" <drew.adams@oracle.com>
To: "Kenichi Handa" <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: RE: composition text property
Date: Mon, 25 Jun 2007 20:07:41 -0700 [thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMAEANDDAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1I2zvN-0001oF-CL@etlken.m17n.org>
Thanks for that explanation, and for offering to clean up the doc.
Perhaps, if this is meant for internal use only, it should not even be
mentioned in the doc? If it is mentioned, and if you need to use
`compose-region' to make use of it, then that should be mentioned too, and
perhaps a short example such as you provided. Again, however, this sounds
like something that we should perhaps not document at all.
prev parent reply other threads:[~2007-06-26 3:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 16:08 composition text property Drew Adams
2007-06-22 22:51 ` Drew Adams
2007-06-26 1:32 ` Kenichi Handa
2007-06-26 3:07 ` Drew Adams [this message]
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=EIENLHALHGIMHGDOLMIMAEANDDAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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).