From: John Hendy <jw.hendy@gmail.com>
To: Peter Neilson <neilson@windstream.net>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: evil-mode and org
Date: Wed, 29 Mar 2017 20:37:16 -0500 [thread overview]
Message-ID: <CA+M2ft8g-G_ph2KGgz_GCjb5Ljb0k2C=2=ZaPMPawaq=2LS0hQ@mail.gmail.com> (raw)
In-Reply-To: <op.yxtbgxcgrns8nc@odin>
On Tue, Mar 28, 2017 at 8:23 AM, Peter Neilson <neilson@windstream.net> wrote:
> On Tue, 28 Mar 2017 08:57:40 -0400, Matt Price <moptop99@gmail.com> wrote:
>
>> I've never used Vim but I see a lot of people online raving about evil
>> mode
>> and how much they love it. I'm considering giving it a whirl after the
>> semester ends & I get some free time. I just wondered whether any heavy
>> org
>> users here on the list use evil, and if so, whether you see pain points
>> within org-mode -- my setup is pretty heavily customized, for instance,
>> and
>> I wonder whether that means it will be quite painful to use evil.
>
>
> You will also find people asking why anyone would ever think of using vim.
> One of those is Aaron Bieber.
> https://blog.aaronbieber.com/2016/01/30/dig-into-org-mode.html
I posted in response to John, but funny enough Aaron gives a talk on
evil-mode as well. From the talk he was a heaaavvvy vim user, so I
think it might be more accurate to say: "why would anyone use vim
*given emacs* (he came from vim, after all)?" Equally strong in his
talk (so I assume his philosophy in general) is: "why would anyone use
emacs keybindings *given vim's*?"
John
>
> I use vim only when unavoidable, and I simply pretend it is ed (of ancient
> Unix days). Or maybe I just use ed. I would not bother trying to use ed to
> access org, and thus would not be tempted to use vi, vim or evil mode for
> org, either. One fine day, long, long ago, I had to use a Vax that did not
> have emacs, vim, vi or ed. It did have whatever DEC was using for an editor,
> but I didn't know how to use it instantly. What to do? What to do? I tried
> running TECO. Yes, it had TECO! Saved! (Sort of.)
>
> Why use vim if emacs is already built into your fingertips?
>
next prev parent reply other threads:[~2017-03-30 1:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 12:57 evil-mode and org Matt Price
2017-03-28 13:23 ` Peter Neilson
2017-03-29 15:12 ` John Kitchin
2017-03-29 17:36 ` Peter Neilson
2017-03-30 1:33 ` John Hendy
2017-03-30 1:37 ` John Hendy [this message]
[not found] ` <e73a5e1e52db498f95cf60c7a983be27@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-29 15:21 ` Eric S Fraga
[not found] <1a0d15aafd944fa3864394d8e212046f@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-29 15:11 ` Eric S Fraga
2017-03-30 10:14 ` Guido Van Hoecke
2017-03-30 17:03 ` Guido Van Hoecke
[not found] ` <2addcb35f67b455ba02295550e5b2ec7@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-30 15:48 ` Eric S Fraga
2017-04-10 12:22 ` Matt Price
[not found] ` <013bacb6be3a49b1b8633fb7d2ad1ddc@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-04-10 14:49 ` Eric S Fraga
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+M2ft8g-G_ph2KGgz_GCjb5Ljb0k2C=2=ZaPMPawaq=2LS0hQ@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=neilson@windstream.net \
/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/org-mode.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).