From: Lynn Winebarger <owinebar@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel <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 07:22:33 -0400 [thread overview]
Message-ID: <CAM=F=bD8z6Oai0CyKUwowQck94r2LYGmjZWz3eP6w=s4w390DA@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmmCf0-tHHfmeqmFe_4CHwKrQPMPTQ4G-9yyNOMOB_5i8Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
On Fri, Aug 26, 2022, 4:26 PM Stefan Kangas <stefankangas@gmail.com> wrote:
> 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.
>
> But you may be right in general. Maybe we should really just delete the
> absolutely antique stuff.
>
I've come across a number of packages where the last published version
still uses the cl library. I had to download the oldest version of Emacs
to get a manual for it to determine how to convert it to cl-lib.
I'm just giving a concrete illustration of why someone may have a relevant
question about a very ancient feature, given the pace at which Emacs truly
evicts support for obsolete features.
Lynn
[-- Attachment #2: Type: text/html, Size: 1638 bytes --]
next prev parent reply other threads:[~2022-08-27 11:22 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
2022-08-27 11:22 ` Lynn Winebarger [this message]
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='CAM=F=bD8z6Oai0CyKUwowQck94r2LYGmjZWz3eP6w=s4w390DA@mail.gmail.com' \
--to=owinebar@gmail.com \
--cc=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.