From: Kendall Shaw <kshaw@kendallshaw.com>
To: help-gnu-emacs@gnu.org
Subject: Re: List of evil ex commands?
Date: Sat, 31 Oct 2015 16:31:44 -0700 [thread overview]
Message-ID: <56354F60.5040606@kendallshaw.com> (raw)
In-Reply-To: <20151031161507195383866@bob.proulx.com>
On 10/31/2015 03:23 PM, Bob Proulx wrote:
> Kendall Shaw wrote:
>> The command :ex is what I have been using in vi since 1982. In vi it
>> switches to ex (the line editor that came after ed) mode.
> What vi program are you using?
>
> I am using 'nvi' because it is the closest to the original BSD vi
> program that is available by free(dom) license. There if I start nvi
> as 'ex' then I am in ex mode. Typing in 'vi' (the ':' is already
> there in ex mode) then I enter visual mode. But in nvi visual mode
> typing in ":ex" does not turn off visual mode. Typing in ":" does
> however allow me to type in any ex command. This is sufficient for
> me. Supposedly in nvi the Q command exits visual mode and returns to
> ex mode but for whatever reason for me it says the Q command is
> unknown. This has never bothered me enough to pursue it further. I
> assume it is simply a bug in the nvi implementation. It hasn't been
> getting much love lately.
>
Sorry, I am conflating some things. My train of thought was that it's
called ex because it switched/switches to ex mode in vi that was on
either Ultrix, Berkeley Unix or SunOS 4.x. But, :ex filename loaded a
file and so that was what muscle memory has been using.
I've been using vim in some form on linux for a long time and nvi on
openbsd just because it is what is/was installed by default.
Kendall
next prev parent reply other threads:[~2015-10-31 23:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 18:42 List of evil ex commands? Kendall Shaw
2015-10-31 19:28 ` Óscar Fuentes
2015-10-31 20:43 ` Kendall Shaw
2015-10-31 22:23 ` Bob Proulx
2015-10-31 23:31 ` Kendall Shaw [this message]
2015-11-01 4:52 ` Random832
2015-11-01 18:59 ` Bob Proulx
2015-11-01 16:07 ` Emanuel Berg
2015-10-31 19:34 ` Random832
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56354F60.5040606@kendallshaw.com \
--to=kshaw@kendallshaw.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.