all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-27 fda6009: Minor copyedits of Emacs manual
Date: Tue, 06 Jul 2021 15:45:17 +0300	[thread overview]
Message-ID: <83pmvvfw6a.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmcB+AAv9CKe==pcGLEBSpvUSqDkbhuJPVJkhRwxigNKw@mail.gmail.com> (message from Stefan Kangas on Tue, 6 Jul 2021 14:30:36 +0200)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Tue, 6 Jul 2021 14:30:36 +0200
> 
> >  Emacs comes with an introductory online tutorial available in many
> > -languages.  This book picks up where that tutorial ends.  It explains
> > -the full range of Emacs's power and contains reference material useful
> > -to expert users.
> > +languages, and this manual picks up where that tutorial ends.  It
> > +explains the full range of the power of Emacs, now up to @strong{version
> > +27.2}, and contains reference material useful to expert users.  It
> > +also includes appendices with specific material about X and GTK
> > +resources, and with details for users of macOS and Microsoft Windows.
> 
> I think the final sentence here could be left out.  The appendices
> aren't super exciting or important in themselves, and the paragraph as
> a whole carries more punch without it.  Just my two cents.

It's a marketing thing, not a technical one.  The text comes from a
person who manages the next printing of the Emacs manual for the FSF
shop.



  reply	other threads:[~2021-07-06 12:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210706115859.24857.52446@vcs0.savannah.gnu.org>
     [not found] ` <20210706115901.4C57E20B72@vcs0.savannah.gnu.org>
2021-07-06 12:30   ` emacs-27 fda6009: Minor copyedits of Emacs manual Stefan Kangas
2021-07-06 12:45     ` Eli Zaretskii [this message]
2021-07-06 16:43       ` Stefan Kangas

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=83pmvvfw6a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stefan@marxist.se \
    /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.