From: Eli Zaretskii <eliz@gnu.org>
To: Tony Kennedy <adk3141@hotmail.com>
Cc: 31143@debbugs.gnu.org
Subject: bug#31143: elisp manual corrections
Date: Fri, 13 Apr 2018 16:54:19 +0300 [thread overview]
Message-ID: <83k1tb5i0k.fsf@gnu.org> (raw)
In-Reply-To: <VI1P190MB0397823C9836831BA974FE65A6BC0@VI1P190MB0397.EURP190.PROD.OUTLOOK.COM> (message from Tony Kennedy on Thu, 12 Apr 2018 23:36:46 +0000)
> From: Tony Kennedy <adk3141@hotmail.com>
> Date: Thu, 12 Apr 2018 23:36:46 +0000
>
> I have made some comments, corrections, and suggestions on the attached PDF copy of the elisp manual. I thought I would send it to you in case you might find it useful.
Thanks for taking time to read the manual and comment on it.
I fixed some typos and other uncontroversial parts of your
suggestions, but left others unhandled, either because they were
already fixed in the current sources (it sounds like you didn't build
the latest version from the Emacs Git repository), or because the
problem was most probably caused by your local configuration (in
particular the fl ligature business: there's nothing wrong with the
Texinfo source in all those cases), or because I disagreed with your
suggestions. And some comments seem to question the implementation,
not the correctness or clarity of the documentation, or generally
raise issues for which I didn't feel the manual is the right place.
For the future, I suggest to send your comments and corrections citing
the Texinfo sources, not as comments to PDF version of the manual,
because the latter is harder to read. (I actually encourage you to
resend these comments in that format, to facilitate their discussion
and application.)
parent reply other threads:[~2018-04-13 13:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <VI1P190MB0397823C9836831BA974FE65A6BC0@VI1P190MB0397.EURP190.PROD.OUTLOOK.COM>]
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=83k1tb5i0k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31143@debbugs.gnu.org \
--cc=adk3141@hotmail.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).