unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: master 55f46cc77c: Decrease use of the word "Emacsen" in docs
Date: Sat, 01 Oct 2022 19:39:15 +0300	[thread overview]
Message-ID: <835yh3birw.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkOSptiAq5UL8ozjMn-+56quxMDqmHzzTDdJS=cB2hV6w@mail.gmail.com> (message from Stefan Kangas on Sat, 1 Oct 2022 18:15:23 +0200)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sat, 1 Oct 2022 18:15:23 +0200
> Cc: emacs-devel@gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > What's wrong with using "Emacsen"?
> 
> When talking about older versions of Emacs, it's just jargony and
> unhelpful.  Better to say what is actually meant.

This is too much.  You are removing words we used for decades in Emacs
development for no good reason.  You think they are "just jargony and
unhelpful", but for me and others this part of our culture and our
history of involvement in the Emacs development.  We treasure that
history.  Right now, I feel like a chunk of my personal history has
been rewritten.

There still are "other Emacsen" out there, even though most of them
are all but moribund nowadays.  But even if they were completely dead,
the word doesn't have to be removed.  It does no harm by just being
there.

I think these changes are misguided.  They go way beyond the
reasonable.  Please don't do that.



  reply	other threads:[~2022-10-01 16:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01 15:21 master 55f46cc77c: Decrease use of the word "Emacsen" in docs Eli Zaretskii
2022-10-01 16:15 ` Stefan Kangas
2022-10-01 16:39   ` Eli Zaretskii [this message]
2022-10-01 17:26     ` Stefan Kangas
2022-10-01 17:50       ` Eli Zaretskii
2022-10-02  0:18     ` Po Lu

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=835yh3birw.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 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).