From: Richard Stallman <rms@gnu.org>
To: Raj Divecha <rjd1977tech@icloud.com>
Cc: 74488@debbugs.gnu.org, eliz@gnu.org
Subject: bug#74488: Why not modernize Emacs
Date: Wed, 27 Nov 2024 23:52:30 -0500 [thread overview]
Message-ID: <E1tGWVy-0002Zc-Fa@fencepost.gnu.org> (raw)
In-Reply-To: <a4550504-e10b-4a80-8bcf-7122e038136b@me.com> (bug-gnu-emacs@gnu.org)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
We don't seek to make Emacs "modern" in the sense changing things to
follow changing fashions. For instance, Lisp still has the advantages
it always had. Even if somene offered to rewrite all our existing
Lisp code into Python, we still prefer Lisp.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
prev parent reply other threads:[~2024-11-28 4:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 23:27 bug#74488: Why not modernize Emacs Raj Divecha via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-23 3:57 ` Stefan Kangas
2024-11-24 4:37 ` Richard Stallman
2024-11-23 6:59 ` Eli Zaretskii
2024-11-25 17:58 ` Raj Divecha via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-25 18:59 ` Eli Zaretskii
2024-11-26 21:58 ` Eduardo Ochs
2024-11-26 22:42 ` Raj Divecha via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-27 4:07 ` Eduardo Ochs
2024-11-27 21:02 ` Raj Divecha via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-28 4:52 ` Richard Stallman [this message]
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=E1tGWVy-0002Zc-Fa@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=74488@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rjd1977tech@icloud.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).