From: Eli Zaretskii <eliz@gnu.org>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Specialized Emacs Features ?
Date: Fri, 02 Jun 2017 16:13:27 +0300 [thread overview]
Message-ID: <838tlacz2g.fsf@gnu.org> (raw)
In-Reply-To: <EA9EB8DA-58A7-4220-BD24-AFFC7CA1D562@gmail.com> (message from Jean-Christophe Helary on Fri, 2 Jun 2017 22:04:57 +0900)
> From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
> Date: Fri, 2 Jun 2017 22:04:57 +0900
>
> >> What's the point of having a separate document for those "specialized" (?) features?
> >
> > To make the printed Emacs user manual smaller.
>
> It makes sense. But it's not clear what's the line between what is "specialized" and what is not...
It's a judgment call.
> Moved to Specialized manual
> • 31 The Calendar and the Diary
> • 32 Sending Mail
> • 33 Reading Mail with Rmail
> • 34 Gnus
> • 38 Web Browsing with EWW
> • 39 Embedded WebKit Widgets
> • 50 Emacs Lisp Packages
> • 51 Customization
These all sound like too important to omit from the user manual.
E.g., how can we omit Customization? Or Emacs Lisp Packages?
next prev parent reply other threads:[~2017-06-02 13:13 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 [this message]
2017-06-02 13:38 ` Jean-Christophe Helary
2017-06-02 14:05 ` Eli Zaretskii
2017-06-02 14:35 ` Jean-Christophe Helary
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=838tlacz2g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@gmail.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).