From: "Peter Neilson" <neilson@windstream.net>
To: emacs-orgmode@gnu.org
Subject: Re: evil-mode and org
Date: Wed, 29 Mar 2017 13:36:14 -0400 [thread overview]
Message-ID: <op.yxvhuoyarns8nc@odin> (raw)
In-Reply-To: <m237dwqfqh.fsf@andrew.cmu.edu>
On Wed, 29 Mar 2017 11:12:22 -0400, John Kitchin <jkitchin@andrew.cmu.edu>
wrote:
> Using evil-mode is not "using vim" IMHO. I think this is a question of
> do you want modal editing or not (I suppose it could also be do you want
> emacs-lisp or vimscript, but that is not the impression I get these days
> ;). With emacs you can have either traditional emacs editing (one-mode:
> edit) or modal editing like vim (for the most part). And you can still
> use emacs-lisp to customize the environment so you can have things like
> org-mode.
>
> I have seen a growing movement towards modal editing in emacs, e.g.
> evil-mode, spacemacs, hydra, avy/ivy, etc... and even do some things
> modally myself with those tools.
Thinking historically, I see modal editing in TECO, where everything
between "i" and "$" (the ESC key) was insert mode, and everything else was
a command. Woe unto the person who omitted the "i" or who inadvertently
ended insert mode, because all other text was commands. For example,
ihxhgh$ inserts "hxhgh" but just hxhgh$ duplicates the entire buffer.
Here is a sample TECO session:
*hkiHere is some text that I am inserting.
Here is another line.
$$
*ht$$
Here is some text that I am inserting.
Here is another line.
*zjiThis is a new bottom line. Next we try forgetting an "i" command.
$$
*here is a forgotten i command
$$
?SYS No such file or directory
?UFI unable to open file e is a forgotten i command<CR><LF> for input
*
next prev parent reply other threads:[~2017-03-29 17:35 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 [this message]
2017-03-30 1:33 ` John Hendy
2017-03-30 1:37 ` John Hendy
[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=op.yxvhuoyarns8nc@odin \
--to=neilson@windstream.net \
--cc=emacs-orgmode@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.
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).