From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Does Richard M. Stallman still scrutinize and develop the codes of Emacs now?
Date: Sun, 15 Aug 2021 09:39:09 +0200 [thread overview]
Message-ID: <878s13rwbm.fsf@zoho.eu> (raw)
In-Reply-To: CAGP6POJ2=kESVRc8s+4WTTEc5xb+E7nUzcFy7EYFvAmGJa4BUQ@mail.gmail.com
Hongyi Zhao wrote:
>>> But I've never seen him on Emacs relevant mailing lists.
>>> Does Richard M. Stallman still scrutinize and develop the
>>> codes of Emacs now?
>>
>> He just sent a message on emacs-devel a few hours ago.
>> Maybe you're not on the right lists.
>
> Really. I checked the emacs-devel list, and it turns out he
> was pretty active there.
I met RMS 2015 in Belgium. He was selling GNU pins for 2 EUR
a piece, it had a cartoonish gnu head on it and the letters
"gnu.org".
I asked, if you buy one, are you then a true follower?
He replied, "it is a way of helping".
It was like if Chairman Mao would sell Che Guevara T-shirts at
a 1st-of-May rally! Maybe for arms to the People's Liberation
Army. But I liked it.
Obviously I bought one, I had it for many years in my
bookshelf, it always made me smile. But it was lost when part
of my conapt was disintegrated.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-08-15 7:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 6:46 Does Richard M. Stallman still scrutinize and develop the codes of Emacs now? Hongyi Zhao
2021-08-15 6:55 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 7:02 ` Jean-Christophe Helary
2021-08-15 7:15 ` Hongyi Zhao
2021-08-15 7:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 7:39 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-08-15 7:17 ` Eli Zaretskii
2021-08-15 7:35 ` Hongyi Zhao
2021-08-15 7:42 ` Hongyi Zhao
2021-08-15 8:08 ` Eli Zaretskii
2021-08-15 8:22 ` Hongyi Zhao
2021-08-15 8:29 ` Stephen Berman
2021-08-15 8:41 ` Hongyi Zhao
2021-08-15 9:28 ` Teemu Likonen
2021-08-15 11:54 ` Hongyi Zhao
2021-08-15 12:45 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 13:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-21 22:05 ` Wayne Harris via Users list for the GNU Emacs text editor
2021-08-22 0:53 ` Jude DaShiell
2021-08-22 1:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 1:14 ` Jude DaShiell
2021-08-22 1:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 7:03 ` tomas
2021-08-22 7:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 17:05 ` Samuel Banya
2021-08-22 17:17 ` Eli Zaretskii
2021-08-22 17:49 ` Arthur Miller
2021-08-22 19:15 ` Samuel Banya
2021-08-23 18:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-23 21:01 ` Tim Johnson
2021-08-25 9:04 ` Jean Louis
2021-08-25 22:25 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 13:43 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 10:08 ` Arthur Miller
2021-08-19 6:13 ` Jean Louis
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=878s13rwbm.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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.
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).