From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: master df8e705eb2 1/2: Don't refer to Emacs 24.3 or older in FAQ
Date: Sat, 27 Aug 2022 09:34:28 +0300 [thread overview]
Message-ID: <83a67q19fv.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmCf0-tHHfmeqmFe_4CHwKrQPMPTQ4G-9yyNOMOB_5i8Q@mail.gmail.com> (message from Stefan Kangas on Fri, 26 Aug 2022 20:24:38 +0000)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Fri, 26 Aug 2022 20:24:38 +0000
> Cc: emacs-devel@gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > What would be the reason to remove references to old Emacs versions
> > from the FAQ? I'm thinking maybe we should simply exempt the FAQ from
> > this process, which is, of course, perfectly valid for the other
> > documentation.
>
> The purpose is mostly just to make the text easier to read, and to make
> it not look outdated. For example, references to this new cool feature
> in Emacs 21 is not likely to be very relevant or helpful in 2022.
Saying that Emacs can do something since version XX.YY can never be
outdated. And I don't think a reference to Emacs 21 can necessarily
be irrelevant or unhelpful nowadays. It depends on what it says and
how it says that.
Thus, changing the wording to reflect the time that has passed is
perfectly fine wherever it makes sense. But removing the text
entirely just because it mentions an old version is IMO wrong for the
FAQ.
> But you may be right in general. Maybe we should really just delete the
> absolutely antique stuff.
Like what, for example?
> > The FAQ is supposed to be a place where people could look for
> > information like "since when does Emacs do this-and-that?".
>
> I was thinking also in terms of confused newcomers, who might be
> overwhelmed by secondary details. (As in: "Wait, which version of Emacs
> am I using? Is it Emacs 22 or newer?")
The FAQ is not a mandatory reading for newcomers, so I'm not sure this
use case is very important. And people nowadays know that the version
of the program they run is supposed to be somewhere in Help->About.
So I think we should only make sure the wording doesn't imply that,
say, Emacs 212 happened yesterday, and otherwise keep the references
to old versions in the FAQ.
next prev parent reply other threads:[~2022-08-27 6:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 18:36 master df8e705eb2 1/2: Don't refer to Emacs 24.3 or older in FAQ Eli Zaretskii
2022-08-25 22:33 ` Stefan Kangas
2022-08-26 5:49 ` Eli Zaretskii
2022-08-26 20:24 ` Stefan Kangas
2022-08-27 6:34 ` Eli Zaretskii [this message]
2022-08-27 11:22 ` Lynn Winebarger
2022-08-27 3:34 ` Richard Stallman
2022-08-27 13:06 ` Lars Ingebrigtsen
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=83a67q19fv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@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 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.