vi was made in an era where 9600 baud and glass teletype are state of the art, and built by poor graduate students of UC Berkeley who cant afford machines running emacs :D
On Tue, Dec 2, 2008 at 6:01 PM, Ludwig Isaac Lim <[EMAIL PROTECTED]> wrote: > > > Hi Thad > > > What is wrong editing with vi in UNIX? Fact is no VIM in UNIX and that > > simplicity works fine and its not inefficient, no need of blinking or > > color highlighted text. I can presume that you are used to Bash and > > having a hard time to navigate around with set -o vi and expecting tab > > completion to work. I will not be surprised if you user account shell > > is Korn you may just need to modify your user profile to suit up what > > you need. > > > > Sorry if I sounded like I'm bashing vi. As I stated in my previous > post, the primary reason > of avoiding an ssh and then a vi is simply because of the slow network, the > response time of > typing is quite slow (Sometimes the characters would appear in the screen > after a second) > > In fairness, I'm not as familiar with vi as compare to vim hence I'm > more productive using > vim. I'm used to certain features of vim such as CTRL-n "auto-complete" > feature (good for > programming), I believe this is not the ESC-ESC auto-complete in ksh; but > I'll check=) > > I don't mind editing scripts in vi, but for large scripts (500+ lines) I > prefer to use vim. > > Regards, > > > > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > http://lists.linux.org.ph/mailman/listinfo/plug > Searchable Archives: http://archives.free.net.ph >
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
