From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs manual for 26.0
Date: Thu, 18 May 2017 18:15:52 +0300 [thread overview]
Message-ID: <83vaoy42mv.fsf@gnu.org> (raw)
In-Reply-To: <CA+cPLChgLd8uF-yt3qKAXRjMgi-27JbwWqUiB2qvDQG-q2KC0Q@mail.gmail.com> (message from 良ϖ on Thu, 18 May 2017 09:01:06 +0000)
> From: 良ϖ <p.de.boisset@gmail.com>
> Date: Thu, 18 May 2017 09:01:06 +0000
> Cc: help-gnu-emacs@gnu.org
>
> On 10/04/2017, Eli Zaretskii <eliz@gnu.org> wrote:
> > It will, when Emacs 26.1 is about to be released.
>
> Any news for the updated edition of Emacs manual for version 26?
>
> Is it possible to get an Emacs manual version in par with the current Emacs?
The manual is generally updated as changes are committed to the
sources, but you seem to want the manual on paper, and that won't be
available until Emacs 26.1 is actually released. That is still far
away.
next prev parent reply other threads:[~2017-05-18 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 8:52 Emacs manual for 26.0 良ϖ
2017-04-10 13:30 ` Eli Zaretskii
2017-05-18 9:01 ` 良ϖ
2017-05-18 15:15 ` Eli Zaretskii [this message]
2017-05-19 0:08 ` Emanuel Berg
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=83vaoy42mv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).