From: Tim Johnson <tim@akwebsoft.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Does Richard M. Stallman still scrutinize and develop the codes of Emacs now?
Date: Mon, 23 Aug 2021 13:01:25 -0800 [thread overview]
Message-ID: <c5b8020b-9ce8-143d-273e-9e073e635709@akwebsoft.com> (raw)
In-Reply-To: <87fsv0rppy.fsf@zoho.eu>
On 8/23/21 10:16 AM, Emanuel Berg via Users list for the GNU Emacs text
editor wrote:
> Samuel Banya wrote:
>
>> The way I think of this is like this:
>>
>> There always will be a fork.
>>
>> Look at Vim:
>> Sure the same guy is still leading major git commits, but
>> most people use Neovim anyway.
>>
>> Same thing with Emacs, especially if they force Rust into
>> the main Emacs repo. That's when I'll start looking for
>> different forks of it as I'm more of a fan of C anyway.
> It's the same thing! Especially if that happens.
Good grief, I never heard of neovim until just now. Have used vim
for ages, especially for adhoc system editing and have evil on emacs.
As much as I've always admired vim, I've been a little concerned that it
appears
to be a one-developer system. Glad to see that emacs has moved away from
that.
cheers
--
Tim
tj49.com
next prev parent reply other threads:[~2021-08-23 21:01 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
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 [this message]
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=c5b8020b-9ce8-143d-273e-9e073e635709@akwebsoft.com \
--to=tim@akwebsoft.com \
--cc=help-gnu-emacs@gnu.org \
/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).