public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jody" <jbruchon@nc.rr.com>
To: Miguel Bolanos <mike@linuxlabs.com>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: *vi*->e3
Date: Fri, 4 Jun 2004 13:37:19 -0400	[thread overview]
Message-ID: <003201c44a5a$9651c5b0$0101a8c0@vash> (raw)
In-Reply-To: 1086357908.3235.5.camel@talena.hsol.net

Replace vi with e3 if you can force e3 to behave just like vi when it
starts, because I used SmallLinux and it invokes e3 when I type vi and I
couldn't edit ANYTHING.  Pissed me off.  It must start as if it is vi and
behave as if it is vi if we are to replace vi with it.  I'm sure others
will agree.  I don't CARE about emacs keybindings because I don't USE
emacs.  I don't want some oddball editor with controls I don't know, I want
something that I can use out of the box.
I personally liked the editor "nano" that was in older Debian releases,
because it had its [control-X] key combinations for commands listed briefly
at the bottom while you used it, it was full-screen, and it behaved like a
"sane" full-screen editor rather than being a creep like vi, where I have
to type :a to add to the end of a line and :i to insert...why can't I just
type and use cursor keys to move around?  Maybe it's not "the traditional
UNIX way of doing it" but it sure helps to not have to accidentally type :i
when I "meant" :a and similar...
I have always hated vi anyway.  The only reason I use CRUX's vi is because
it's vim and vim lets me type :i and then break all the vi typing rules :)
I can use vi though, so if we're talking about replacing it with something
smaller, AT LEAST MAKE SURE IT WORKS THE SAME WHEN INVOKED.  I don't want
to have to figure out a new editor, and indeed we would like a very small
learning curve between ELKS <-> Linux day-to-day console work.
I used to use MS-DOS EDIT back in DOS 5.0, but you sure as heck NEVER saw
me using EDLIN for ANYTHING AT ALL.  Line editors are old and outdated.
Full-screen editors with menus or control-X combinations that are
explicitly outlined at the bottom are much easier and friendly and sane,
especially to people who haven't used UNIX or ELKS before.

Courtesy of the Highly Opinionated vi-hating Jody, who still uses Windows
despite the fact that Linux is better.
----- Original Message -----
From: "Miguel Bolanos" <mike@linuxlabs.com>
To: "Tommy McCabe" <rocketjet314@yahoo.com>
Cc: <linux-8086@vger.kernel.org>
Sent: Friday, June 04, 2004 11:25 AM
Subject: Re: *vi*->e3




  reply	other threads:[~2004-06-04 17:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 18:51 *vi*->e3 Tommy McCabe
2004-06-04 15:25 ` *vi*->e3 Miguel Bolanos
2004-06-04 17:37   ` Jody [this message]
2004-06-04 20:32     ` *vi*->e3 Tommy McCabe
2004-06-04 17:45   ` *vi*->e3 Albrecht Kleine
2004-06-05  2:41     ` *vi*->e3 Miguel Bolanos
2004-06-09 13:42 ` *vi*->e3 Miguel Bolanos

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='003201c44a5a$9651c5b0$0101a8c0@vash' \
    --to=jbruchon@nc.rr.com \
    --cc=linux-8086@vger.kernel.org \
    --cc=mike@linuxlabs.com \
    /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