[Info-vax] Intel proposal to simplify x86-64

[Dan Cross]

In article <mddo7lo2nd4.fsf at panix5.panix.com>,
Rich Alderson  <news at alderson.users.panix.com> wrote:
>jgd at cix.co.uk (John Dallman) writes:
>
>> In article <u5s84c$1fo4c$1 at dont-email.me>, news at cct-net.co.uk (Chris
>> Townley) wrote:
>
>>> I do know vi(m) and use it a lot on Unix/Linux systems - like EVE 
>>> on VMS it is always there. However I choose not to use it for more 
>>> than simple changes - I would never use it to write any code
>
>> I found vi baffling on first exposure, and the only commands I know in it
>> are for getting out again. If vi or vim is the available screen editor,
>> I'll resort to ed or ex. 
>
>I only know enough vi to edit the password file (using the vipw command), or in
>the old days before autoconfiguration I could edit the Emacs configuration files
>to install a decent editor.

Over the years,I've found it useful to retain facility with
several different editors, selecting between them based on
context.  If I'm working on plan9, I'll use acme or sam; if
I'm on Unix, vi, though knowing how to use `ed` has been very
useful in many surprising ways; if I'm programming in Lisp, or
using Multics or TOPS-20, then emacs; on VMS I use EDT; etc.
For work-a-day programming these days I like VS Code with the
language server support.

	- Dan C.