From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Specialized Emacs Features ?
Date: Fri, 2 Jun 2017 23:35:57 +0900 [thread overview]
Message-ID: <7C19A7A0-22C6-4CE6-9C66-683000F6B6EE@gmail.com> (raw)
In-Reply-To: <837f0ucwog.fsf@gnu.org>
> On Jun 2, 2017, at 23:05, Eli Zaretskii <eliz@gnu.org> wrote:
>
> You should talk to the FSF about this, it is they who publish printed
> manuals and sell them. I have no idea what they consider when they
> decide on these issues.
Ok.
>> • I'm not finding the "specialized" manual in Info mode.
>
> IOW, the chapters of this manual are chapters and sections in the
> Emacs manual in Info format. There's no separate manual in Info.
I was naively looking for a separate manual in the main Info ToC. Apologies.
>> • The emacs manual is *not* an introductory manual, so I don't think we should have an "Advanced Features" section where most of the chapters could actually be placed in sections that relate to their contents (as I kind of proposed in the re-shuffling I sent in my earlier mail).
>
> You interpret "Advanced" too literally in this case. I think it's a euphemism.
:) Yes, but the "Advanced Features" section is a mess that should be reorganized.
Jean-Christophe
next prev parent reply other threads:[~2017-06-02 14:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 12:13 Specialized Emacs Features ? Jean-Christophe Helary
2017-06-02 12:22 ` Eli Zaretskii
2017-06-02 13:04 ` Jean-Christophe Helary
2017-06-02 13:13 ` Eli Zaretskii
2017-06-02 13:38 ` Jean-Christophe Helary
2017-06-02 14:05 ` Eli Zaretskii
2017-06-02 14:35 ` Jean-Christophe Helary [this message]
2017-06-02 14:56 ` Yuri Khan
2017-06-02 15:11 ` Jean-Christophe Helary
2017-06-02 15:55 ` Eli Zaretskii
2017-06-02 16:15 ` Jean-Christophe Helary
2017-06-02 17:34 ` Eli Zaretskii
2017-06-02 23:46 ` Jean-Christophe Helary
2017-06-02 23:55 ` Clément Pit-Claudel
2017-06-03 0:49 ` Jean-Christophe Helary
2017-06-03 6:15 ` Eli Zaretskii
2017-06-03 6:33 ` Jean-Christophe Helary
2017-06-04 2:56 ` Richard Stallman
2017-06-03 6:09 ` Eli Zaretskii
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=7C19A7A0-22C6-4CE6-9C66-683000F6B6EE@gmail.com \
--to=jean.christophe.helary@gmail.com \
--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).