unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
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, 22 Aug 2021 03:02:53 +0200	[thread overview]
Message-ID: <871r6m1ebm.fsf@zoho.eu> (raw)
In-Reply-To: alpine.NEB.2.23.451.2108212049580.26971@panix1.panix.com

Jude DaShiell wrote:

> Last I read on an article comparing emacs and vim, Stephen
> Monier had the emacs lead passed to him by Richard Stallman
> and the fact that emacs has a line of succession made it
> different from vim in that vim had no clear line of
> succession. At that time the lead developer of vim hadn't
> designated anyone to take over development when the original
> lead developer of vim could no longer continue developing
> for whatever reason.

Ha, what is this, Medieval Europe?

I'm sure Vim has a maintainer just like Emacs ...

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2021-08-22  1:02 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
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 [this message]
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=871r6m1ebm.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).