11-20-2003
I agree with linuxpenguin. Working with multiple UNIX flavors at multiple companies, I tend to lean towards the lowest common factor. I know that I'll find vi everywhere I work. The same can't be said of custom editors, emacs etc. There is power in vi that people often overlook (buffers, typecasting etc.)
Cheers,
Keith
6 More Discussions You Might Find Interesting
1. 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
2. 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
3. SuSE
Hi,
One of our applications has this string :
xxx ¿ yyyyy
We are on Linux Suse and the character set is en_US.UTF-8. Our requirement is to replace this special character ¿ with a space. When we open the file containing this string using VI editor we see the same character as <92>
xxx... (10 Replies)
Discussion started by: LinuxTest
10 Replies
4. Linux
Hi I have a process generating a file in Solaris. Now we have migrated the process to Linux. When we open the file in vi on solaris and hit space bar, it stops after reaching the end of line. But in linux it continues to go on the next line. So I want to know whether the difference is between the... (4 Replies)
Discussion started by: sudhamacs
4 Replies
5. HP-UX
Hi All,
I am comfortable working in LINUX and need equivalents for HP-UX for below mentioned,
1. We use TAB key to expand/reveal a name in LINUX. Is there any way to make this work for UNIX, where it is double escape.
2. Also can we use make use of left,down,up,right keys instead... (3 Replies)
Discussion started by: pradebban
3 Replies
6. What is on Your Mind?
We have asked UNIX.com users over the years what is their favorite editor and why. Here is the top three answers.
Here is a new YT video on this question:
What Editor Does Everyone Use?
https://youtu.be/gqE8RTZZt9g
Of course, vi was the overwhelming favorite.
Credits:
1080 HD... (3 Replies)
Discussion started by: Neo
3 Replies
emacs(1) General Commands Manual emacs(1)
NAME
emacs, xemacs - emacs editor
DESCRIPTION
The emacs software is unsupported software that is provided as part of Tru64 UNIX. Compaq will fix problems in this unsupported software
only if they are specific to Tru64 UNIX. Compaq will not fix problems that are integral to the software itself or that occur when the com-
ponent is used on UNIX systems other than Tru64 UNIX. Compaq will not add functionality to this software.
Except for this reference page, other reference pages that Tru64 UNIX supplies for emacs are passed through without changes. The reference
pages distributed as part of this software are available in the directories /usr/share/doclib/annex/man/man[1-9]. You should use this
directory stem in the man command or add it to the MANPATH environment variable to make these files available to the man command.
Note
Compaq is not responsible for the content or quality of reference pages and other documents installed under the /usr/share/doclib/annex
directory and does not revise this material in response to customer problem reports. Reference pages installed under the
/usr/share/doclib/annex/man directory are not available from Compaq in book form; for example, they are not included in the reference manu-
als that you receive when you order the Tru64 UNIX documentation set as hard copy books.
Problems related to the content or quality of any documentation installed in the /usr/share/doclib/annex directory tree should be sent to
the developers of the documentation.
The format for changing the search path with the man command is: man -P /usr/share/doclib/annex/man [section] title...
If you are using the Bourne, Korn, or POSIX shells, use the following command sequence to modify your environment: MANPATH=$MAN-
PATH:/usr/share/doclib/annex/man export MANPATH
If you are using the C shell, enter the command: setenv MANPATH `echo $MANPATH`:/usr/share/doclib/annex/man
See the reference pages for the man(1) command for additional information on the search path used to locate files.
The reference pages associated with this product are not included in the whatis data base created by the catman command. Therefore, the
man -k and apropos commands will not locate reference pages included with this product.
SEE ALSO
Commands: apropos(1), catman(8), man(1)
emacs(1)