From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 3568@debbugs.gnu.org, larsi@gnus.org
Subject: bug#3568: 23.0.94; no doc for character composition
Date: Thu, 28 Apr 2016 08:07:40 +0300 [thread overview]
Message-ID: <83h9emxqw3.fsf@gnu.org> (raw)
In-Reply-To: <c9f2afff-2575-44f6-8e68-f6fc4e631c58@default> (message from Drew Adams on Wed, 27 Apr 2016 14:18:20 -0700 (PDT))
> Date: Wed, 27 Apr 2016 14:18:20 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: larsi@gnus.org, 3568@debbugs.gnu.org
>
> > > What the bug report mentions. I don't think that a doc string for
> > > one command covers this topic.
> >
> > Well, I think it does. You could change my mind by telling what is it
> > that you miss in that doc string.
>
> I'd like an explanation of character composition, in the Elisp manual.
Would copying the doc string of compose-region into the manual do what
you want? If not, what in that doc string is missing or not explained
well enough?
> As one user, I know nothing about this. And I still know nothing
> about it after reading that doc string. FWIW.
I don't understand this claim. You certainly know what the doc string
says, which is definitely not "nothing".
Is this a serious bug report? If it is, would you please help me
understand what is missing in the documentation, by at least answering
my questions, if not by elaborating some more about the problem? TIA.
prev parent reply other threads:[~2016-04-28 5:07 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
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 [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=83h9emxqw3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=3568@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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 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).