Sponsored Content
Top Forums Programming Open Source What editor does everyone use? Post 77769 by Neo on Tuesday 12th of July 2005 05:26:45 PM
Old 07-12-2005
Quote:
Originally Posted by zazzybob
I agree that vi is the way to go. And if you know vi, you'll be able to use line editors such as ex and ed when you're using some screwy old terminal or coming in via a really slow modem or serial link.

Learning vi is a *huge* investment, and will be an invaluable skill to add to your Unix skillset....

BTW for those who are unsure - vi is pronounced Vee Eye. We've got people at work who pronounce it "Vie" and that is definitely not the done thing Smilie How we snigger Smilie

Cheers
ZB

A beautiful ex-girlfriend of mine (should have married her!), at my prodding years ago, wrote her entire masters thesis in VI. When she graduated from her University she landed a nice paying UNIX job at Lycos.De because, of her great UNIX/VI skills. VI pays $$$ !!!! Smilie
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Vi editor ?

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

instead VI editor - which one?

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

vi editor

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

best editor

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

vi editor

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

Pasting text in VI editor from a different editor

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

set EDITOR=vi -> default editor not setting for cron tab

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 :Licen

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

About vi editor

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

Not able to use @ in VI editor

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
SKILL(1)							   User Commands							  SKILL(1)

NAME
skill, snice - send a signal or report process status SYNOPSIS
skill [signal] [options] expression snice [new priority] [options] expression DESCRIPTION
These tools are obsolete and unportable. The command syntax is poorly defined. Consider using the killall, pkill, and pgrep commands instead. The default signal for skill is TERM. Use -l or -L to list available signals. Particularly useful signals include HUP, INT, KILL, STOP, CONT, and 0. Alternate signals may be specified in three ways: -9 -SIGKILL -KILL. The default priority for snice is +4. Priority numbers range from +20 (slowest) to -20 (fastest). Negative priority numbers are restricted to administrative users. OPTIONS
-f, --fast Fast mode. This option has not been implemented. -i, --interactive Interactive use. You will be asked to approve each action. -l, --list List all signal names. -L, --table List all signal names in a nice table. -n, --no-action No action; perform a simulation of events that would occur but do not actually change the system. -v, --verbose Verbose; explain what is being done. -w, --warnings Enable warnings. This option has not been implemented. -h, --help Display help text and exit. -V, --version Display version information. PROCESS SELECTION OPTIONS
Selection criteria can be: terminal, user, pid, command. The options below may be used to ensure correct interpretation. -t, --tty tty The next expression is a terminal (tty or pty). -u, --user user The next expression is a username. -p, --pid pid The next expression is a process ID number. -c, --command command The next expression is a command name. --ns pid Match the processes that belong to the same namespace as pid. --nslist ns,... list which namespaces will be considered for the --ns option. Available namespaces: ipc, mnt, net, pid, user, uts. SIGNALS
The behavior of signals is explained in signal(7) manual page. EXAMPLES
snice -c seti -c crack +7 Slow down seti and crack commands. skill -KILL -t /dev/pts/* Kill users on PTY devices. skill -STOP -u viro -u lm -u davem Stop three users. SEE ALSO
kill(1), kill(2), killall(1), nice(1), pkill(1), renice(1), signal(7) STANDARDS
No standards apply. AUTHOR
Albert Cahalan <albert@users.sf.net> wrote skill and snice in 1999 as a replacement for a non-free version. REPORTING BUGS
Please send bug reports to <procps@freelists.org> procps-ng October 2011 SKILL(1)
All times are GMT -4. The time now is 02:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy