Sponsored Content
Full Discussion: Vim compatible
Top Forums UNIX for Dummies Questions & Answers Vim compatible Post 302960034 by sabsac on Monday 9th of November 2015 09:44:30 PM
Old 11-09-2015
Wrench

Please see attached image.I am in insert mode when I clicked the screenshot but I dont see the syntax prompt at the bottom of the screen.Also on starting this editor it says I am in vim compatible mode.
Vim compatible-screenshot-2015-11-09-18-28-52png
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Print Servers compatible with Solaris

Does anyone have any advice on what print servers to use with Solaris I used to use intel but they dicontinued the model we used. I would just use lpadmin to set them up . Any advice on this would be very helpful. (2 Replies)
Discussion started by: xmildx
2 Replies

2. Linux

VPN compatible with NAT

Hey, i was wondering if anybody knew of a good VPN that is compatible with nat? If a VPN will not work with NAT could it work with PAT? Right now i'm using RH9. I wanted to use IPsec but i don't think that is compatiable with nat or pat. Please correct me if i'm wrong. Thanks, Byblyk. (0 Replies)
Discussion started by: byblyk
0 Replies

3. Linux Benchmarks

Gd2 not compatible with Clientexec

Dear Frnds We are having WHM Cpanel in which many website are their , one of our customer want to install Clientexec software which requires GD2.0.28(compatible) library which is installed. The problem is libpng version which is incompatible with the GD library . Please kindly... (0 Replies)
Discussion started by: naik_mit
0 Replies

4. UNIX for Dummies Questions & Answers

winzip compatible command

Dear friends, I m new to Unix, can anybody please guide me on how to zip and password protect a normal text (or any file) in unix prompt? (1 Reply)
Discussion started by: topgear1000cc
1 Replies

5. 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

6. Hardware

is rhel 6 compatible with dell xps 14

is rhel 6 compatible with dell xps 14.I tried to install it but could not install.Installation hanged at detecting hardware (1 Reply)
Discussion started by: shamapraveen
1 Replies

7. Hardware

Trying to find a compatible OS for an old computer

Hello A friend and I recently got our hands on an old computer (a rainbow '83 I think), cleaned it, etc... And now we're trying to get the thing running. The problem is that the included OS is badly documented, so I thought of installing an old version of UNIX on it. So the questions are: Is that... (8 Replies)
Discussion started by: ijiboom
8 Replies

8. Shell Programming and Scripting

To make my script multi-os compatible

Hi, I would like to make my script multi-os compatible and I am having problems to make it work. I would like it to be compatible with those 4 linux versions : Ubuntu, Debian, Fedora and Centos. I am mostly confused when it comes to the repository installation and the different os... (1 Reply)
Discussion started by: gaaara
1 Replies

9. Shell Programming and Scripting

Looking for a perl-compatible regex solution

This is for PHP preg_match code - which is PCRE therefore looking for a perl compatible suggestion I have this line returned I want to match and return.. I want to match the two instances of string ending 'ABCXYZ' into an array. And on second element (ie. RootABCXYZ) only return the word... (4 Replies)
Discussion started by: deadyetagain
4 Replies

10. Shell Programming and Scripting

Compatible awk command

the following command works beautifully. it basically grabs the content of a file from First to End, then excludes any lines containing specific patterns. awk '/^First/,/^End$/ {if (!/#\/bin\/sh|not.*commonly|#/) print}' datafile. i never had any issues with the command until I ran it on a... (5 Replies)
Discussion started by: SkySmart
5 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 06:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy