Solved

vi - do I need to learn it?

Posted on 2000-03-19
4
332 Views
Last Modified: 2013-12-06
I am running a UNIX server to run a manager of a network security software. I wonder if I need to learn vi ... as such I dont use it much right now.
I started learning it...and using it is so very cumbersome. IS there any other easier and more user-friendly text editor? why is vi used anyway, when it is so un-user-friendly? if its widely used then I do  need to learn it, right?

please help
0
Comment
Question by:java_lover
  • 2
4 Comments
 
LVL 40

Accepted Solution

by:
jlevie earned 30 total points
ID: 2634801
Well, no you don't have to use it. There are lots of alternatives, which ones depend on what Unix you are on. However, vi remains popular because it requires very little resources and in the case of needing to edit a file in single user mode it may be the only editor that works. I don't routinely use vi, preferring xemacs instead, but there are plenty of times that I use vi for a quick, simple edit of a small file. For a really simple edit, I can almost have it done before xemacs is fully up and ready to use. Knowing how to use the basic vi functions is a good thing.
0
 

Expert Comment

by:chansek
ID: 2634894
Hello

   If it is possible, learn VI editor. The only reason for that is all UNIX boxes like HP-UX, SUN, AIX, SCO or etc. They all have VI editor. You learn VI editor, then you could apply it anywhere. Also, you could fully manipulate the VI tools (utilities like to call file name, recall/check historical commands and etc.) in shell environment especially KORN shell.
OR
  EMACS editor is another tool for you. But, no all UNIX boxes has EMACS editor.
  Good luck.
0
 

Author Comment

by:java_lover
ID: 2638509
I wonder why its so different and hence tedious to learn. Has there been any effort in maintaining its simplicity but still make it more user-friendly?
0
 
LVL 40

Expert Comment

by:jlevie
ID: 2638542
The reason is mostly historical in nature. You have to understand that vi came about in the days when terminals were very primitive compared to what we have today. An editor was needed that could work on anything and in those days (and to some degree even today) everybody that made a terminal had their own idea of how it would work and what you could do with it. If you want to get some idea of the number of terminals, take a look through a termcap file sometime. Accordingly was structured to require only the minimum capabilities from a terminal.

Even as arcane as it looks like vi is, it was, at the time, a major improvement over what it replaced. Prior to vi, one used ed, which is a line editor. Take a look at the man page for ed and try it sometime. I think you'll find that vi is a vast improvement.
0

Featured Post

3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Unistall fileset without dependecies on AIX 3 68
Using Grep to Find a file 8 93
Linux : can't create transaction lock error 1 67
awk sed 8 45
I have been running these systems for a few years now and I am just very happy with them.   I just wanted to share the manual that I have created for upgrades and other things.  Oooh yes! FreeBSD makes me happy (as a server), no maintenance and I al…
Using libpcap/Jpcap to capture and send packets on Solaris version (10/11) Library used: 1.      Libpcap (http://www.tcpdump.org) Version 1.2 2.      Jpcap(http://netresearch.ics.uci.edu/kfujii/Jpcap/doc/index.html) Version 0.6 Prerequisite: 1.      GCC …
Learn several ways to interact with files and get file information from the bash shell. ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:

803 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question