From: "Scott B. Berry" <n7zib@tritel.net>
To: <blinux-list@redhat.com>
Subject: Re: info about vi on the net
Date: Thu, 19 Sep 2002 09:41:03 -0600 [thread overview]
Message-ID: <00ba01c25ff4$b98a4220$3ea0a6d8@scottscomp> (raw)
In-Reply-To: <20020919112842.0af05b10.gandre@arkeia.com>
Okay here is the deal. I am using Debian 2.25r2 and I am actually trying to
set up a win modem. I did find a quick reference guide for this for right
now. I don't really like the editor because it doesn't have commands at the
botom to get me out of trouble if some thing were to happen on accident say
I hit escape one too many times and I get thrown in the command mode instead
of the insert mode. However I have learned a few things and this quick
reference is what I need for the time being as I just trying to configure
the system.
Scott Berry
Msn: electronicman1960@hotmail.com
Yahoo Messenger: electronicman1960
If you are interested in scanning and you are blind please come join our
police scanner list. To subscribe send a message to:
mailto:blindscanner-subscribe@yahoogroups.com
----- Original Message -----
From: "Gil Andre" <gandre@arkeia.com>
To: <blinux-list@redhat.com>
Sent: Thursday, September 19, 2002 3:28 AM
Subject: Re: info about vi on the net
>
> Scott,
>
> I think you need to include more information about what you
> are trying to do or to learn.
>
> For instance : which distribution of Linux are you using?
>
> Most distributions of Linux (Red Hat, Mandrake) do not use
> "vi", but supply the more advanced "vim" and make a symlink
> from "vi" to "vim".
>
> If you are using Slackware, though, "vi" is linked to "elvis",
> which is a little bit less advanced than "vim" (but still
> better than plain old "vi").
>
> Etc... etc... you get my drift.
>
> Try entering the following command:
> which vi
>
> And do an "ls" on the directory it returns to have more info
> on the vi you are using on your system.
>
> Second:
>
> What would you like to know? With a lot of UNIX programs, the
> best way is to start by entering the following command:
> apropos vi
>
> or, to filter the results:
> apropos vi | less
> apropos vi | grep editor
> apropos vi | grep tutor
>
> This will give you less information, but also information that's
> more relevant. Simply enter the name of the program you'd like
> more information on, as such:
> man <name-of-program>
>
> For instance, here are all the interesting man pages I could find
> on my Slackware 8.1 machine:
>
> bash-2.05a$ apropos vi | grep edit
> elvis (1) - a clone of the ex/vi text editor
> evim (1) - easy Vim, edit a file with Vim and setup
> for modeless editing
> vim (1) - Vi IMproved, a programmers text editor
> vimdiff (1) - edit two or three versions of a file with
> Vim and show differences
> vimtutor (1) - the Vim tutor
>
> Finally, I can send you a PS file that was created as a very, very
> short documentation for vi -- this is almost the only documentation
> that I use for vim, as it contains all the really helpful commands.
>
> Also, try entering the command "vimtutor", as it will launch a very
> helpful tutorial on vim.
>
> On Wed, 18 Sep 2002 10:10:42 -0600, Scott wrote:
> > Are there any goo d sites where I can get more info about vi on the net.
I
> > did try vitutor vi-tutor vilearn vi-learn with no success.
>
> I hope this helps!
>
> --
>
> Gil Andre ___ Technical writer ___ Arkeia Corporation
> email: gandre@arkeia.com | web: http://www.arkeia.com
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Scott B. Berry
` Henry Yen
` Jude DaShiell
` Scott B. Berry
` Jude DaShiell
` Jude DaShiell
` John
` Gil Andre
` Scott B. Berry [this message]
` Gil Andre
` Hans Zoebelein
` John
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='00ba01c25ff4$b98a4220$3ea0a6d8@scottscomp' \
--to=n7zib@tritel.net \
--cc=blinux-list@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).