|
|
Sponsored Content
Top Forums
Programming
Open Source
What editor does everyone use?
Post 302076931 by reborg on Friday 16th of June 2006 07:09:50 PM
06-16-2006
Administrator Emeritus
Quote:
Originally Posted by mrprietzel
Glad to find this discussion since it deals directly with something that has been vexing me for a while.
I'm fairly new to unix and was disappointed when unix friends told me "just use vi" when I asked for the best way to edit and view files on our solaris boxes.
I have come to the conclusion that I need 2 editors in the unix world
Editor #1 - for use when I am writing code, scripts, etc. In other words editing that is going to take me more than a minute. For this I use Jedit
Editor #2 - Used for quickly editing, searching and viewing files. I frequently need to edit a single line in a file, or need to view the file or search its contents (I know about grep, but I like to see the results of my search in the context of the rest of the file). For Editor #2 I'm not sure what to use. I have almost come to the conclusion that I need to make peace with vi and just accept it, but I find it so frustrating that it takes me longer to check my cheat sheet to find the right commands than it does to actually do the editing. My requirements for Editor #2 are:
-Easily edit, view, and search text files.
-Reasonable amount of certainty that the editor is available. My job requires that I connect to different boxes and often su to a different userid. It is frustrating to learn to use a tool and then it is not available.
-Using the editor is easy to remember. I only need editor #2, two or three times a month. I feel like I am constantly relearning vi, and feel like I'm flying blind when I get lost between command mode and edit mode.
-Needs to run in the console, i.e. doesn't run in X, which for me takes too long to load. I think our network is slow and our boxes are distributed.
-I only need basic functionality, in other words I would trade ease of use in exchange for the advanced features in vi.
Can anyone make a recomendation for Editor #2 or do I need to make my peace with vi
.
I started using pico and liked it a lot but a co-worker told me not to trust it as it truncates lines over 80 characters. Too bad since I really liked it. Anyone know if there is a fix or work around for this.
Basically I'm looking for something like pico or like "edit" from the dos prompt.
I'm fairly new to unix and was disappointed when unix friends told me "just use vi" when I asked for the best way to edit and view files on our solaris boxes.
I have come to the conclusion that I need 2 editors in the unix world
Editor #1 - for use when I am writing code, scripts, etc. In other words editing that is going to take me more than a minute. For this I use Jedit
Editor #2 - Used for quickly editing, searching and viewing files. I frequently need to edit a single line in a file, or need to view the file or search its contents (I know about grep, but I like to see the results of my search in the context of the rest of the file). For Editor #2 I'm not sure what to use. I have almost come to the conclusion that I need to make peace with vi and just accept it, but I find it so frustrating that it takes me longer to check my cheat sheet to find the right commands than it does to actually do the editing. My requirements for Editor #2 are:
-Easily edit, view, and search text files.
-Reasonable amount of certainty that the editor is available. My job requires that I connect to different boxes and often su to a different userid. It is frustrating to learn to use a tool and then it is not available.
-Using the editor is easy to remember. I only need editor #2, two or three times a month. I feel like I am constantly relearning vi, and feel like I'm flying blind when I get lost between command mode and edit mode.
-Needs to run in the console, i.e. doesn't run in X, which for me takes too long to load. I think our network is slow and our boxes are distributed.
-I only need basic functionality, in other words I would trade ease of use in exchange for the advanced features in vi.
Can anyone make a recomendation for Editor #2 or do I need to make my peace with vi
. I started using pico and liked it a lot but a co-worker told me not to trust it as it truncates lines over 80 characters. Too bad since I really liked it. Anyone know if there is a fix or work around for this.
Basically I'm looking for something like pico or like "edit" from the dos prompt.
|
|
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello everybody,
My question is: how to add /tmp/work at the end of line in vi editor.
my file looks like:
cp file1
cp file2
cp file3
****
I need to add " /tmp/work" at the end of each line.
I tried this
:%s/$/" /tmp/work"
and this
:%s/$/\ /tmp/work\/
but it does not work. (2 Replies)
Discussion started by: billy5
2 Replies
2. HP-UX
I'd like to find some editor for HP-UX, something like notepad, but not VI editor. Can someone have some ideas which one?
thx (6 Replies)
Discussion started by: diamond
6 Replies
3. UNIX for Advanced & Expert Users
Hi,
how can I add at the begining and at the end of all of the lines of my text file in VI editor ? Many thanks before.
for exemple if in my file i have
line 1
line 2
I want to have :
start line 1 end
start line 2 end (3 Replies)
Discussion started by: alain123456
3 Replies
4. UNIX Desktop Questions & Answers
We work on AIX 5L
We use vi as text editor (only scripts to create and modifiy).
What do you think of emacs ? Where can I find it ?
Do you know better text editor for scripts ?
Thank you for all answers. (1 Reply)
Discussion started by: annemar
1 Replies
5. HP-UX
I am new in hp ux and I want work with vi editor, but in hp ux vi editor the backspaes and del keys doesn't work.
how can I enable them.
thanks (3 Replies)
Discussion started by: hkoolivand
3 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question.
How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'?
As i see, p & P options does work only within 'vi'. (10 Replies)
Discussion started by: harishmitty
10 Replies
7. Shell Programming and Scripting
Hi All,
I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by
set EDITOR=vi it does not open a vi editor , rather it do as below.....
/////////////////////////////////////////////////////
$ set... (6 Replies)
Discussion started by: aarora_98
6 Replies
8. Solaris
Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
9. Shell Programming and Scripting
How can ` character be printed on vi editor ?
empl_id=`echo $line | awk ' { print $1; } '` (2 Replies)
Discussion started by: senem
2 Replies
10. Shell Programming and Scripting
Hello All,
Need one Help for one issue.
I am using a French Keyboard, so @ sign is on key 0 and i have to use right Alt + 0 to print it.
It is working everywhere but not inside Vi editor. I can type @ in shell, in notepad. But inside Vi editor it is not working, another problem is that if... (2 Replies)
Discussion started by: yadavricky
2 Replies
LEARN ABOUT BSD
edit
EX(1) General Commands Manual EX(1) NAME
ex, edit - text editor SYNOPSIS
ex [ - ] [ -v ] [ -t tag ] [ -r ] [ +command ] [ -l ] name ... edit [ ex options ] DESCRIPTION
Ex is the root of a family of editors: edit, ex and vi. Ex is a superset of ed, with the most notable extension being a display editing facility. Display based editing is the focus of vi. If you have not used ed, or are a casual user, you will find that the editor edit is convenient for you. It avoids some of the complexi- ties of ex used mostly by systems programmers and persons very familiar with ed. If you have a CRT terminal, you may wish to use a display based editor; in this case see vi(1), which is a command which focuses on the display editing portion of ex. DOCUMENTATION
The document Edit: A tutorial (USD:14) provides a comprehensive introduction to edit assuming no previous knowledge of computers or the UNIX system. The Ex Reference Manual - Version 3.7 (USD:16) is a comprehensive and complete manual for the command mode features of ex, but you cannot learn to use the editor by reading it. For an introduction to more advanced forms of editing using the command mode of ex see the editing documents written by Brian Kernighan for the editor ed; the material in the introductory and advanced documents works also with ex. An Introduction to Display Editing with Vi (USD:15) introduces the display editor vi and provides reference material on vi. In addition, the Vi Quick Reference card summarizes the commands of vi in a useful, functional way, and is useful with the Introduction. FILES
/usr/share/misc/exstrings error messages /usr/libexec/exrecover recover command /usr/sbin/expreserve preserve command /etc/termcap describes capabilities of terminals ~/.exrc editor startup file /tmp/Exnnnnn editor temporary /tmp/Rxnnnnn named buffer temporary /usr/preserve preservation directory SEE ALSO
awk(1), ed(1), grep(1), sed(1), grep(1), vi(1), termcap(5), environ(7) AUTHOR
Originally written by William Joy Mark Horton has maintained the editor since version 2.7, adding macros, support for many unusual terminals, and other features such as word abbreviation mode. BUGS
The undo command causes all marks to be lost on lines changed and then restored if the marked lines were changed. Undo never clears the buffer modified condition. The z command prints a number of logical rather than physical lines. More than a screen full of output may result if long lines are present. File input/output errors don't print a name if the command line `-' option is used. There is no easy way to do a single scan ignoring case. The editor does not warn if text is placed in named buffers and not used before exiting the editor. Null characters are discarded in input files, and cannot appear in resultant files. 4th Berkeley Distribution October 21, 1996 EX(1)