* Re: emacs-28 ddabb03a01: * doc/misc/idlwave.texi (Troubleshooting): Don't say "Emacsen".
[not found] ` <20220906212731.448E8C0088A@vcs2.savannah.gnu.org>
@ 2022-09-06 21:30 ` Philip Kaludercic
2022-09-06 21:35 ` Stefan Kangas
0 siblings, 1 reply; 2+ messages in thread
From: Philip Kaludercic @ 2022-09-06 21:30 UTC (permalink / raw)
To: emacs-devel; +Cc: Stefan Kangas
Stefan Kangas <stefankangas@gmail.com> writes:
> branch: emacs-28
> commit ddabb03a0176beb4b7fc8d4f2267d459fd2ebded
> Author: Stefan Kangas <stefankangas@gmail.com>
> Commit: Stefan Kangas <stefankangas@gmail.com>
>
> * doc/misc/idlwave.texi (Troubleshooting): Don't say "Emacsen".
Is there a reason the term should not be used?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: emacs-28 ddabb03a01: * doc/misc/idlwave.texi (Troubleshooting): Don't say "Emacsen".
2022-09-06 21:30 ` emacs-28 ddabb03a01: * doc/misc/idlwave.texi (Troubleshooting): Don't say "Emacsen" Philip Kaludercic
@ 2022-09-06 21:35 ` Stefan Kangas
0 siblings, 0 replies; 2+ messages in thread
From: Stefan Kangas @ 2022-09-06 21:35 UTC (permalink / raw)
To: Philip Kaludercic; +Cc: Emacs developers
Philip Kaludercic <philipk@posteo.net> writes:
> Is there a reason the term should not be used?
It's just less clear than saying "Emacs", which is what we mean here.
We also recommend against using it in the FAQ, see the node on "What
was XEmacs".
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-09-06 21:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <166249965095.21111.7331163151785383963@vcs2.savannah.gnu.org>
[not found] ` <20220906212731.448E8C0088A@vcs2.savannah.gnu.org>
2022-09-06 21:30 ` emacs-28 ddabb03a01: * doc/misc/idlwave.texi (Troubleshooting): Don't say "Emacsen" Philip Kaludercic
2022-09-06 21:35 ` Stefan Kangas
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).