12-13-2012
Quote:
Originally Posted by
AZbase10
Hardcore UNIX noob here. I'm not shocked to see vi(m) so high on the list.
Learning to use vi is so easy, I've done it dozens of times.
It is...eccentric, and
not designed for a modern keyboard. But knowing vi can make or break your ability to fix an unfamiliar system. Knowing the very, very basics has been crucial to me a few times. (esc :wq = quit and save, esc :q! = quit without saving, esc esc esc = stop doing whatever I turned on by accident, esc i = stop beeping at me and let me type already you stupid program, esc d d = delete the line)
Also, the pico editor is a bit old, wedded to the
pine mailing program, and has some problems as a general-purpose editor(its insistence on linewrapping everything, a horrible thing to do to a script or configfile). nano is the modern equivalent if you can get it, the pico interface plus a little more. You'll find it more places than you find pico these days.
Last edited by Corona688; 12-13-2012 at 11:00 PM..
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
TALK(1) BSD General Commands Manual TALK(1)
NAME
talk -- talk to another user
SYNOPSIS
talk person [ttyname]
DESCRIPTION
Talk is a visual communication program which copies lines from your terminal to that of another user.
Options available:
person If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on
another host, then person is of the form 'user@host'.
ttyname If you wish to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal
name, where ttyname is of the form 'ttyXX' or 'pts/X'.
When first called, talk contacts the talk daemon on the other user's machine, which sends the message
Message from TalkDaemon@his_machine...
talk: connection requested by your_name@your_machine.
talk: respond with: talk your_name@your_machine
to that user. At this point, he then replies by typing
talk your_name@your_machine
It doesn't matter from which machine the recipient replies, as long as his login name is the same. Once communication is established, the
two parties may type simultaneously; their output will appear in separate windows. Typing control-L (^L) will cause the screen to be
reprinted. The erase, kill line, and word erase characters (normally ^H, ^U, and ^W respectively) will behave normally. To exit, just type
the interrupt character (normally ^C); talk then moves the cursor to the bottom of the screen and restores the terminal to its previous
state.
As of netkit-ntalk 0.15 talk supports scrollback; use esc-p and esc-n to scroll your window, and ctrl-p and ctrl-n to scroll the other win-
dow. These keys are now opposite from the way they were in 0.16; while this will probably be confusing at first, the rationale is that the
key combinations with escape are harder to type and should therefore be used to scroll one's own screen, since one needs to do that much less
often.
If you do not want to receive talk requests, you may block them using the mesg(1) command. By default, talk requests are normally not
blocked. Certain commands, in particular nroff(1), pine(1), and pr(1), may block messages temporarily in order to prevent messy output.
FILES
/etc/hosts to find the recipient's machine
/var/run/utmp to find the recipient's tty
SEE ALSO
mail(1), mesg(1), who(1), write(1), talkd(8)
BUGS
The protocol used to communicate with the talk daemon is braindead.
Also, the version of talk(1) released with 4.2BSD uses a different and even more braindead protocol that is completely incompatible. Some
vendor Unixes (particularly those from Sun) have been found to use this old protocol.
Old versions of talk may have trouble running on machines with more than one IP address, such as machines with dynamic SLIP or PPP connec-
tions. This problem is fixed as of netkit-ntalk 0.11, but may affect people you are trying to communicate with.
HISTORY
The talk command appeared in 4.2BSD.
Linux NetKit (0.17) November 24, 1999 Linux NetKit (0.17)