From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Compositions documentation
Date: Fri, 06 Feb 2009 21:00:52 -0500 [thread overview]
Message-ID: <jwvy6wjj9ba.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <umycztwrm.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 Feb 2009 17:23:09 +0200")
> I see that the Lisp APIs that deal with compositions
> (composition-get-gstring, compose-region, compose-string,
> find-composition, etc.) are not documented in the ELisp manual.
> Should they be? Or are these APIs so obscure that no one should futz
> with them?
FWIW, `compose-region' is used in the "pretty lambda" trick, which
I have adapted to sml-mode, haskell-mode, and a bunch of others.
Stefan
next prev parent reply other threads:[~2009-02-07 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 15:23 Compositions documentation Eli Zaretskii
2009-02-07 2:00 ` Stefan Monnier [this message]
2009-02-10 6:26 ` 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=jwvy6wjj9ba.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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).