unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: Vim project helps in Uganda, Emacs shall be next
Date: Sun, 21 Feb 2021 09:56:52 +0300	[thread overview]
Message-ID: <YDIENAV6j16hFok6@protected.rcdrun.com> (raw)
In-Reply-To: <877dn22b0k.fsf@zoho.eu>

* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2021-02-21 09:33]:
> Jean Louis wrote:
> 
> > It really does not matter what are goals of Vim or GNU
> > project
> 
> The Emacs-Vim $EDITOR war... that was ages ago.

I have no idea about the war, but where there are wars there are
veterans. They never forget. ;-)

For me it does not matter, I use sometimes nvi as vi, and Vim and Gvim
sometimes, e3em as Emacs emulation, zile, zile-on-guile, nano, but
mostly Emacs. I like Emacs in console as it is more consistent with
`mutt' email reader, and I use Emacs in console also on my mobile
devices. Today extensible editors like Vim and Emacs may emulate each
other. Differences are in speed and bloat.

viper-mode is interesting feature of Emacs but if I invoke M-x
viper-mode in GUI, then it does not reflect same in console, it is not
global mode how I see it. Sometimes "emacsclient -nw"
blocks.

I can use basic key bindings of vi editors in Emacs, and I think it is
equally well as Emacs key bindings.

Modal modes would allow much more key prefixes, that is also something
to think about.

Combination of key bindings also work well.

It is often pleasure to use vi key bindings in Emacs. I wonder why no
Spacemacs users are reporting to this mailing list.

No conflicts between editors on my side.



  reply	other threads:[~2021-02-21  6:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 14:14 Vim project helps in Uganda, Emacs shall be next Jean Louis
2021-02-16 18:59 ` Philip Kaludercic
2021-02-16 19:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-17  4:50   ` Jean Louis
2021-02-17 17:54     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-17  5:12 ` Pankaj Jangid
2021-02-21  6:14   ` Jean Louis
2021-02-21  6:24     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-21  6:56       ` Jean Louis [this message]
2021-02-21  7:48         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-21  8:55           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-21  9:18             ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-21 12:46             ` Jean Louis
2021-03-02  3:27               ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-02  3:42               ` Emanuel Berg via Users list for the GNU Emacs text editor

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=YDIENAV6j16hFok6@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --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).