From: rhodesia@wixer.cactus.org (Felix S. Gallo)
Subject: Re: IS UNIX DEAD? (long)
Followup-To: comp.unix.questions
Organization: Real/Time Communications
Date: Tue, 10 Nov 92 05:53:11 GMT

papresco@napier.uwaterloo.ca (Paul Prescod) writes:
>Why is it, in VI if I try to save a file without a name it doesn't prompt
>me for a name?  Instead it kicks me back to vi.  Or if I try to quit without
>saving.  Why doesn't it ask me "Save y/n."  There is no reason VI couldn't
>have an "expert" mode that got rid of messages for those that don't want
>them.

Hey, why doesn't my toaster ask me for confirmation if I press the little
bar without inserting any bread?

As a matter of fact, there are implementations of vi (which is not a
monolithic single-source program) which do this.  There are also 
*innumerable* easy editors which you may install on your fine system.

>Why is it, in VI that there is no way (I know of) to get help, or exit,
>without knowing the exit key?  What doesn't "h" in command mode present
>ANY kind of help?

Why doesn't my hard drive realize that I didn't really want to delete
that data?  Why don't I have a team of ergonomics specialists sitting
at my desk doing all my typing by dictation?

Again, vi is not a drop-in replacement for Microsoft Write.  It's
an extremely powerful editor of text files.  If you want to whine,
consider asking Microsoft why they don't have a command line in
their editors.

>Why is it, in RN that when I hit 'h' to ask about how to find a command,
>it doesn't give me a menu "message read commands","post commands" "misc
>commands."  Instead it makes me read two pages of (mostly useless) commands.

The command you wanted to use was doubtless on one of those two pages.
What do you want, hypertext pop up windows?  The common Unix user wants
to get work done.

>Why don't Unix "tools" have a convention about help and exit keys AT THE
>VERY LEAST.  

Control-C works for me.  That, or Control-Z kill %1.

>Where am I supposd to get help about VI?  The man pages tell me nothing
>except how to load it.

Your lack of attentiveness is simply not our problem.  The bottom of
every man page I've seen about 'vi' contains a pointer to the actual
vi manual.

>Why do I have 12 function keys on my keyboard that seem to do absolutely
>nothing?


dumb question is this?  Are you blaming your keyboard manufacturer's
ills on Unix, or are you incoherently expecting that Unix assign some
sort of meaning to every key assignable?
>
>Why doesn't VI use the jkl; keys for cursor movement, since your fingers
>are already on them.  Or why not use keys somewhere far from them.  A
>person can easily get confused.

Whose fingers are already on them?  Not mine.  If you're having a hard
time moving your fingers one key away, might I recommend not using
a computer?  These things are dangerous.

>Why doesn't help do anything in SH (and others).

'help' is not /bin/sh's problem.  /bin/bash seems to have taken up
that banner, but it's pretty clear to me that 'help' as a shell level
command could shadow a system-specific 'help' which could actually
provide a useful function.

It seems to me that you're yet another user who's been dropped into
Unix cold, without any sort of manual or helpful administrator around.
You have my sympathy for being clueless.

>Why doesn't help do anything in VI?

You already asked this question.

>Why does VI default to beeping at you when you try to type as opposed to
>editing?

Because you're Making a Mistake, and vi appropriately tells you so.

>Why is it that if I want to WordProcess in VI I have to remember to hit return at the end of the line otherwise bizarre things happen.  Why not just wrap, beep, or slide over (i.e. let the line go long). 

Again, you're confused.  My vi, and every vi I have used, has dealt with
too-long lines in a rational manner.  All my vis also have word-wrap,
which you would discover if you took the time to read the man page and
read the manual listed at the end of the man page.

>Is there a wordwrap mode in VI?  And if so, why doesn't it kick in when I
>use VI from RN?

a) yes.  b) because your .exrc file is not set up correctly.

>Inquiring minds want to know.

Hey, I'm getting into the rhythm of this.  Let me try:

Why is it that people who have no idea how to use Unix and who think
that it should operate at the lowest common denominator keep asking
stupid questions?
-- 
----------------------------------------------------------------------------
Felix Sebastian Gallo                              rhodesia@wixer.cactus.org
----------------------------------------------------------------------------