RE: Editing a file in linux

[vhamberg@xxxxxxxxxxx]

I suggest RTFM - you have to get to the man pages, as the help text is called 
in tne various *ix OS's. on a command line in Linux just type man vi to get the 
help for that command/utility.

I recommend getting into an X Windows session and use one of the more graphical 
editors. You might need a VNC client - I am told realVNC is good. I forget what 
I used to use. The VNC server has to have been started in Linux. There you have 
several options, and if you really want a good time, try emacs.

Finding the docs can be a bit daunting in the *ix world, but the info is out 
there. There might even be stuff in InfoCenter!!

HTH
Vern


-------------- Original message -------------- 
From: rob@xxxxxxxxx 

> hqlinux:/etc # echo $EDITOR 
>
> hqlinux:/etc # apropos editor 
> pdisk (8) - Apple partition table editor for Linux 
> ex (1) - Vi IMproved, a programmers text editor 
> vi (1) - Vi IMproved, a programmers text editor 
> rvim (1) - Vi IMproved, a programmers text editor 
> ex (1p) - text editor 
> ed (1) - text editor 
> vi (1p) - screen-oriented (visual) display editor 
> psed (1) - a stream editor 
> s2p (1) - a stream editor 
> sed (1p) - stream editor 
> rview (1) - Vi IMproved, a programmers text editor 
> jfs_debugfs (8) - shell-type JFS file system editor 
> gvim (1) - Vi IMproved, a programmers text editor 
> rgvim (1) - Vi IMproved, a programmers text editor 
> red (1) - text editor 
> joe (1) - Joe's Own Editor 
> rjoe (1) - Joe's Own Editor 
> jpico (1) - Joe's Own Editor 
> zshzle (1) - zsh command line editor 
> rgview (1) - Vi IMproved, a programmers text editor 
> vim (1) - Vi IMproved, a programmers text editor 
> view (1) - Vi IMproved, a programmers text editor 
> gview (1) - Vi IMproved, a programmers text editor 
> jstar (1) - Joe's Own Editor 
> jmacs (1) - Joe's Own Editor 
> atobm (1x) - bitmap editor and converter utilities for the X 
> Window System 
> FvwmConsoleC.pl (1) - Command editor for FVWM command input interface 
> editres (1x) - a dynamic resource editor for X Toolkit 
> applications 
> bitmap (1x) - bitmap editor and converter utilities for the X 
> Window System 
> bmtoa (1x) - bitmap editor and converter utilities for the X 
> Window System 
> xedit (1x) - simple text editor for X 
> hqlinux:/etc # 
>
> Ok, I tried a few, like ed and sed. They looked like they weren't doing 
> anything. Could be because of the way I shut down my session to get out 
> of the editor (stupid user mistake, I know). So I tried vi. That let me 
> know that I was a stupid user and how to recover. I was able to get it 
> done using that editor and a link to a site (thanks for the google tip. 
> First hit worked fine.) 
>
> Now I am going to go home promptly at 5, drink, and work with heavy 
> equipment. And if I get that job done, discharge and clean my 
> muzzleloader. 
>
> Rob Berendt 
> -- 
> Group Dekko Services, LLC 
> Dept 01.073 
> PO Box 2000 
> Dock 108 
> 6928N 400E 
> Kendallville, IN 46755 
> http://www.dekko.com 
>
>
>
>
>
> AGlauser@xxxxxxxxxxxx 
> Sent by: midrange-l-bounces@xxxxxxxxxxxx 
> 05/03/2007 02:58 PM 
> Please respond to 
> Midrange Systems Technical Discussion 
>
>
> To 
> Midrange Systems Technical Discussion 
> cc 
>
> Fax to 
>
> Subject 
> RE: Editing a file in linux 
>
>
>
>
>
>
> Rob Berendt wrote on 03/05/2007 14:52:19: 
>
> > Heck I don't know what editor I am using. Just whatever pops up when 
> you 
> > type the command 
> > edit 
> > in when you are at a suse command line. 
>
> Try typing 'echo $EDITOR' at the command line - this will let you know 
> what the EDITOR environment variable holds. I think that might tell you 
> the default editor. 
>
> Attention: 
>
> The information contained in this message and or attachments is 
> intended only for the person or entity to which it is addressed and may 
> contain 
> confidential and/or privileged material. Any review, retransmission, 
> dissemination or other use of, or taking of any action in reliance upon, 
> this 
> information by persons or entities other than the intended recipient is 
> prohibited. If you received this message in error, please contact the 
> sender and 
> delete the material from any system and destroy any copies. Thank you for 
> your 
> time and consideration. 
>
> Attention: 
>
> Le contenu de ce message et(ou) les fichiers ci-joints sâ??adressent 
> exclusivement à la personne ou -entité à laquelle ils sont destinés. Ils 
> peuvent 
> contenir de lâ??information confidentielle, protégée et(ou) classifiée. Il 
> est 
> strictement interdit à toute personne ou entité autre que le(la) 
> destinataire 
> prévu(e) de ce message dâ??examiner, de réviser, de retransmettre ou de 
> diffuser 
> cette information, de prendre une quelconque action en fonction ou sur la 
> base 
> de celle-ci, ou dâ??en faire tout autre usage. Si vous avez reçu ce message 
> par 
> erreur, veuillez communiquer avec lâ??expéditeur(trice), supprimer ce 
> message et 
> les fichiers ci-inclus de tout système, et en détruire toutes copies, 
> quâ??elles 
> soient électroniques ou imprimées. Nous vous remercions de votre entière 
> collaboration. 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
>
>
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l.