From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Pertinent NEWS parts for the Emacs 26 manual draft
Date: Sat, 30 Sep 2017 09:56:32 +0300 [thread overview]
Message-ID: <83377465en.fsf@gnu.org> (raw)
In-Reply-To: <E1dy3Fb-0002S0-Lk@fencepost.gnu.org> (message from Richard Stallman on Fri, 29 Sep 2017 17:55:15 -0400)
> From: Richard Stallman <rms@gnu.org>
> CC: emacs-devel@gnu.org
> Date: Fri, 29 Sep 2017 17:55:15 -0400
>
> > > THe parts to include are those about changes in user commands and
> > > user-visible behavior, but excluding changes in modes that are not
> > > documented in the Emacs manual (which is most of them).
>
> > Maybe I misunderstand, but don't the "+++" markers in NEWS already
> > tell that?
>
> Whether the +++ markings are a reliable guide depends on the state of
> work on NEWS. They might not yet have been put in; they might have
> been removed. An item might have a --- instead, put there because
> someone mistakenly thought that item isn't pertinent to the Emacs
> Manual.
Since I've already asked Nicolas to make a pretest for Emacs 26.1, it
should be clear that NEWS was already reviewed (by me in this case),
and any such blunders, if there were ones, were already fixed.
> Supposing that at present all pertineny items have a +++ marking, they
> don't necessarily refer to the Emacs Manual; some indicate that a
> feature has been documented in the Emacs Lisp Manual.
NEWS has separate sections for Lisp and non-Lisp changes.
next prev parent reply other threads:[~2017-09-30 6:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 22:08 Pertinent NEWS parts for the Emacs 26 manual draft Richard Stallman
2017-09-29 10:07 ` Eli Zaretskii
2017-09-29 21:55 ` Richard Stallman
2017-09-30 6:56 ` Eli Zaretskii [this message]
2017-09-30 23:14 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2017-10-09 18:16 Richard Stallman
2017-09-21 18:26 Richard Stallman
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=83377465en.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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.