Sponsored Content
Top Forums UNIX for Dummies Questions & Answers VIM Editor - To disable the status on existing Post 302780975 by greenworld123 on Friday 15th of March 2013 10:28:55 AM
Old 03-15-2013
VIM Editor - To disable the status on existing

When i exist the vim editor .. to gives '0' in the console... i think it is status of the exit..
How to disable that ...
 

10 More Discussions You Might Find Interesting

1. Programming

vim editor

in vim editor, if i want to save that file, i have to save and exit (ZZ). i want to be able to save the file without exiting. that way, i can compile the code and if i need to change some coding, i can just switch over without retyping "vim myprogram.c". is there a way to save without exit?... (7 Replies)
Discussion started by: bb00y
7 Replies

2. UNIX for Dummies Questions & Answers

vim as command line editor

Here is my problem, I manage a SunOs 5.8 Server, vi is the default command line editor, I have a line on each users .kshrc profile as follows: export EDITOR=/bin/vi I want to use vim as the command line editor, the below line doesn't work export EDITOR=/bin/vim Thank you (1 Reply)
Discussion started by: tony3101
1 Replies

3. UNIX for Advanced & Expert Users

Ctags in VIM Editor

Hi, I want to use ctags for multiple folders containing .c and .h files. Can anyone help me with it? I have been using ctags for 1 folder at a time but I would like to link multiple folders and access all .c files at a time using ctags. Thanks, shahsm (1 Reply)
Discussion started by: shahsm
1 Replies

4. UNIX for Dummies Questions & Answers

Syntax coloring for .pc files in VIM editor

Hi, i am using VIM editor through Putty. By the option of Syntax on in .vimrc file i am able to see syntax colors in .c and .cpp files but not in the files with .pc extension. How can this be done? :confused: (2 Replies)
Discussion started by: RuchK
2 Replies

5. UNIX for Dummies Questions & Answers

tip: Simple script won't run in cygwin - vim editor involved

I ran into this issue and thanks to various postings in various forums, was able to figure out the solution but didn't see one posting that laid the whole issue out cleanly. So thought the following might help others ... ------------------------------------------------------------------------... (2 Replies)
Discussion started by: oxysep
2 Replies

6. UNIX for Advanced & Expert Users

vim editor -> uncounted new line

Hi, I entered the following text in a new file through vim: "Four score and seven years ago" saved and exit. When I looked at the file size, it was 31B, although is supposed to be 30. I reedited the file (again with vim) to check for errors, but everything seemed fine. When I opened the file... (3 Replies)
Discussion started by: prostiiinet
3 Replies

7. UNIX for Dummies Questions & Answers

the turn on color in vim editor

how to turn on the color in vim editor."syntax on" is not working for me. when i do syntax on it only make some of the text basically header files nd functions name in bold.i am working on "secure crt" ..my vim is in /usr/share i also have .vimrc file in my home folder "~" Please help me... (11 Replies)
Discussion started by: ascetic
11 Replies

8. Solaris

Very Importan - Vim Settings - Error while opening a File using vim

I downloaded vim.7.2 and compiled the vim source . Added the vim binary path to PATH (Because iam not the root of the box) when i load the file using vim it throws me an error Error detected while processing /home2/e3003091/.vimrc: line 2: E185: Cannot find color scheme darkblue line... (0 Replies)
Discussion started by: girija
0 Replies

9. Red Hat

SSL/TLS renegotiation DoS -how to disable? Is it advisable to disable?

Hi all Expertise, I have following issue to solve, SSL / TLS Renegotiation DoS (low) 222.225.12.13 Ease of Exploitation Moderate Port 443/tcp Family Miscellaneous Following is the problem description:------------------ Description The remote service encrypts traffic using TLS / SSL and... (2 Replies)
Discussion started by: manalisharmabe
2 Replies

10. UNIX for Beginners Questions & Answers

Vim, vi and nano editor shows help.txt automatically

Hi, Whenever i try to open a file in any editor like vi, vim and nano i get this help.txt showing up in split screen without any key being pressed. This continues to pop up even when i close the help.txt. This behavior happens only when i am connected via putty. Is there a fix to this issue? ... (1 Reply)
Discussion started by: sunil0391
1 Replies
VIM(1)							      General Commands Manual							    VIM(1)

NAME
vim - Vi IMproved, a programmers text editor SYNOPSIS
vim [options] [file ..] vim [options] -t tag vim [options] -e [errorfile] DESCRIPTION
Vim is a text editor that is upwards compatible to vi. It can be used to edit any ASCII text. It is especially useful for editing programs. There are a lot of enhancements above vi: multi level undo, multi windows and buffers, command line editing, filename completion, on-line help, visual selection, etc.. Read difference.doc for a summary of the differences between vi and Vim. Most often Vim is started to edit a single file with the command vim file More generally VIM is started with: vim [options] [filelist] If the filelist is missing, the editor will start with an empty buffer. Otherwise exactly one out of the following three may be used to choose one or more files to be edited. file .. A list of file names. The first one (alphabetically) will be the current file and read into the buffer. The cursor will be positioned on the first line of the buffer. You can get to the other files with the ":next" command. -t {tag} The file to edit and the initial cursor position depends on a "tag", a sort of goto label. {tag} is looked up in the tags file, the associated file becomes the current file and the associated command is executed. Mostly this is used for C programs. {tag} then should be a function name. The effect is that the file containing that function becomes the current file and the cursor is positioned on the start of the function (see reference.doc, section "tag searches"). -e [errorfile] Start in quickFix mode. The file [errorfile] is read and the first error is displayed. If [errorfile] is omitted the file name is obtained from the 'errorfile' option (defaults to "AztecC.Err" for the Amiga, "errors" on other systems). Further errors can be jumped to with the ":cn" command. See reference.doc section 5.5. OPTIONS
The options, if present, must precede the filelist. The options may be given in any order. -r Recovery mode. The swap file is used to recover a crashed editing session. The swap file is a file with the same file name as the text file with ".swp" appended. See reference.doc, chapter "Recovery after a crash". -v View mode. The 'readonly' option will be set. You can still edit the buffer, but will be prevented from accidently overwriting a file. If you do want to overwrite a file, add an exclamation mark to the Ex command, as in ":w!". The -v option also implies the -n option (see below). The 'readonly' option can be reset with ":set noro" (see reference.doc, options chapter). -b Binary. A few options will be set that makes it possible to edit a binary or executable file. +[num] For the first file the cursor will be positioned on line "num". If "num" is missing, the cursor will be positioned on the last line. +/pat For the first file the cursor will be positioned on the first occurrence of "pat" (see reference.doc, section "pattern searches" for the available search patterns). +{command} -c {command} {command} will be executed after the first file has been read. {command} is interpreted as an Ex command. If the {command} con- tains spaces it must be enclosed in double quotes (this depends on the shell that is used). Example: Vim "+set si" main.c -x (Amiga only) Vim is not restarted to open a new window. This option should be used when Vim is executed by a program that will wait for the edit session to finish (e.g. mail). The ":sh" and ":!" commands will not work. -o[N] Open N windows. When N is omitted, open one window for each file. -n No swap file will be used. Recovery after a crash will be impossible. Handy if you want to edit a file on a very slow medium (e.g. floppy). Can also be done with ":set uc=0". Can be undone with ":set uc=200". -s {scriptin} The script file {scriptin} is read. The characters in the file are interpreted as if you had typed them. The same can be done with the command ":source! {scriptin}". If the end of the file is reached before the editor exits, further characters are read from the keyboard. -w {scriptout} All the characters that you type are recorded in the file {scriptout}, until you exit VIM. This is useful if you want to create a script file to be used with "vim -s" or ":source!". -T terminal Tells Vim the name of the terminal you are using. Should be a terminal known to Vim (builtin) or defined in the termcap file. -d device Open "device" for use as a terminal. Only on the Amiga. Example: "-d con:20/30/600/150". SEE ALSO
Vim documentation: reference.doc: A complete reference of Vim (long) windows.doc: Explanation of the multi windows and buffers commands and options index: Overview of all command characters (useful when adding new mappings) difference.doc: Overview of the differences between vi and Vim unix.doc: Unix-specific comments vim.hlp: File used by the on-line help (short) AUTHOR
Most of VIM was made by Bram Moolenaar. VIM is based on Stevie, worked on by: Tim Thompson, Tony Andrews and G.R. (Fred) Walter BUGS
Probably. 1994 August 12 VIM(1)
All times are GMT -4. The time now is 02:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy