What type of problem you have encountered with 'vi' ?
The main problem i'm having with vi is, that i understand how to open a file on specific line, the thing I don't get is how to save the changes. For example, I've been trying to do something like this.
As I said, it only opened editor in Insert mode.
It's probably silly me
I've tried to use sed, and it helped, although that was the code I've found on Internet, but I don't understand completely the meaning of criterias yet.
p.s. I've managed to solve the given example using temp file, which is being an absolutely time and space consuming solution....
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)
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)
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)
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)
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)
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)
I was looking through the topics and I wasn't sure if this was the best place to post this question:
I was wondering, out of curiosity, which software everyone was using to code their scripts in. I do mostly sh/ksh and my favorite has always been EditPlus because it is small, fast, yet powerful.... (409 Replies)
Discussion started by: yongho
409 Replies
LEARN ABOUT MOJAVE
intro
INTRO(9) BSD Kernel Developer's Manual INTRO(9)NAME
intro -- introduction to system kernel interfaces
DESCRIPTION
This section contains information about the interfaces and subroutines in the kernel.
PROTOTYPES ANSI-C AND ALL THAT
Yes please.
We would like all code to be fully prototyped.
If your code compiles cleanly with cc -Wall we would feel happy about it. It is important to understand that this isn't a question of just
shutting up cc, it is a question about avoiding the things it complains about. To put it bluntly, don't hide the problem by casting and
other obfuscating practices, solve the problem.
INDENTATION AND STYLE
Believe it or not, there actually exists a guide for indentation and style. It isn't generally applied though.
We would appreciate if people would pay attention to it, and at least not violate it blatantly.
We don't mind it too badly if you have your own style, but please make sure we can read it too.
Please take time to read style(9) for more information.
NAMING THINGS
Some general rules exist:
1. If a function is meant as a debugging aid in DDB, it should be enclosed in
#ifdef DDB
#endif /* DDB */
And the name of the procedure should start with the prefix DDB_ to clearly identify the procedure as a debugger routine.
SCOPE OF SYMBOLS
It is important to carefully consider the scope of symbols in the kernel. The default is to make everything static, unless some reason
requires the opposite.
There are several reasons for this policy, the main one is that the kernel is one monolithic name-space, and pollution is not a good idea
here either.
For device drivers and other modules that don't add new internal interfaces to the kernel, the entire source should be in one file if possi-
ble. That way all symbols can be made static.
If for some reason a module is split over multiple source files, then try to split the module along some major fault-line and consider using
the number of global symbols as your guide. The fewer the better.
SEE ALSO style(9)HISTORY
The intro section manual page appeared in FreeBSD 2.2.
BSD December 13, 1995 BSD