:)

but vi is installed as default on nearly every *nix box, so if you learn
vi, your made. Its not that hard, I recommend The Vi Quick Reference from
O'Reilly.

Shouldn't be used by very new users though, as they will probably wreck
there machine :(

Fran

----------
> From: Paul Derbyshire <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: [newbie] RE: your mail
> Date: 10 February 2000 16:45
> 
> At 10:08 AM 2/10/00 -0000, you wrote:
> >use vi, type vi <filename> at a command prompt, useful commands are:
> >
> >:write - to save
> >:quit - to quit
> >:quit! - to force quit
> >
> >btw. you will probably hate it :)
> 
> Shame on you, suggesting than a new user use vile and then giving an
> inadequate warning. I stumbled on vile once on some machine or other
where
> I had a shell account. Yugh. It doesn't work the way you'd expect (for
> example, you can't open the file, arrow around, and type new text; as
near
> as I can tell it opens all files in a read-only mode and expects a
command
> to be issued to change it) and there's no help to be had hitting F1 and
no
> helpful status line on the screen telling you what key you should hit for
> documentation -- bad interface design, since the interface should work
the
> way people are used to (e.g. for an editor, arrow around and type stuff,
> shift-arrows to select, etc.), and shouldn't require a mini-course from
> Algonquin or thorough reading of the manual. Manuals/help files are for
> reference and how-to, not for basic explaining of the interface. I think
> whoever perpetrated vi was the same idiot who perpetrated Lotus Notes
(see
> http://www.iarchitect.com/mshame.html IIRC -- if that's 404, try just
> http://www.iarchitect.com and click the nice icon of a bomb ;-)).
> 
> PICO, on the other hand, is an okay shell editor.
> If it's not on your system, you'll probably find it on rpmfind.net
> somewhere under 'p'.
> 
> Kedit, of course, works in a way that should be familiar to users of
modern
> graphical systems like 'doze and MacOS. Except for a quirk in that it
seems
> to clobber the clipboard spuriously sometimes, especially if you select
> something -- meaning if you do the usual "select in window A, hit ctrl-C,
> switch to window B, select some old crud, and hit ctrl-V to replace the
old
> crud with the stuff from window B" it won't work in kedit or the
derivative
> kwrite :-(
> 
> -- 
>    .*.  "Clouds are not spheres, mountains are not cones, coastlines are
not
> -()  <  circles, and bark is not smooth, nor does lightning travel in a
>    `*'  straight line."   
-------------------------------------------------
>         -- B. Mandelbrot  |http://surf.to/pgd.net
[EMAIL PROTECTED]
> _____________________ ____|________                          Paul
Derbyshire
> Programmer & Humanist|ICQ: 10423848|

Reply via email to