08-12-2009
Always use vi..
Just love the shortcuts it provide.....
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 LINUX
normality
normality(5) File Formats Manual normality(5)
NAME
normality - definition of what types of normalities different users may have.
SYNOPSIS
/etc/normality
DESCRIPTION
The normality configuration file has a rather simple syntax, as shown in the diagram in the next section. Some things to remember is that
the normality file's influence is inversely proportional to the user's cluefulness and that, in certain cirumstances, modification of the
normality file can and will be considered immoral.
NORMALITY GRAMMAR
<normality file> := <normality file> <line> |
;
<line> := <normality type> ': ' <userlist> |
<normality type> '! ' <userlist> |
<normality type> '= ' <normality tags> |
<comment>
<normality type> := [A-Z][a-zA-Z0-9]+
<userlist> := <username> ', ' <userlist> ';0 |
<username> ';0
<normality tags> := <normality tag> ', ' <normality tags> ';0 |
<normality tag> ';0
<normality tag> := 'marriage' |
'love-relation' |
'nice-job' |
'money' |
'spare-time' |
'friends' |
'no-pager' |
'vacation'
<comment> := '#' .* '0
SEMANTICS
It is expected that you specify all normality types before you start assigning (or disassigning) users to (or from) them. That is so the
system can do an easier consistency check of the specification.
Let's say that we have a system with three normality types, foo, bar and gazonk and two users, cucumber and onion.
Now, a line like "foo! onion;" would exclude onion from having any of the real-life things specified by the foo type, even if that (or
those) things appear in another normality type. So, the disallow syntax overrides the allow syntax (specified by "<type>: <username>...").
There is always an implicit type named ``all'', that contains all normality tags.
For all system administrators, you have an implicit rule, "all! asr".
EXAMPLES
# Normality file for a sad system
# Our users are onion, cucumber, jdoe, jrl and washu
animetype= love-relation, nice-job, friends, spare-time;
notworst= love-relation, nice-job, friends;
sysadm= friends;
# All normality types we will use are declared
# Now let's do the magic stuff...
all: jdoe, jrl;
animetype: washu;
sysadm: cucumber;
all! onion;
# Now, this is fairly easy, OK?
WARNINGS AND BUGS
This file messes with the real world, so a bit of caution is recommended. Newer versions of the chastise(3) library function modifies this
file on-the-fly.
Has a tendecy to create small discontinuities in the velvet of reality whenever there are syntax errors in the normality file.
AUTHOR
This sick idea was put down in *roff format by Ingvar Mattsson, as a contribution to the alt.sysadmin.recovery man page collection.
4th Berkeley Distribution Release 0.001 alpha normality(5)