Sponsored Content
Full Discussion: saving macros for VIM
Top Forums UNIX for Dummies Questions & Answers saving macros for VIM Post 302117367 by reborg on Sunday 13th of May 2007 07:18:53 PM
Old 05-13-2007
I suggest you get a bit more familiar with the rules of this forum. Profanity is not tolerated.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

troff macros

Hi, I'm going write a small handbook. The typesetting software I'm going to use is troff. There are -ms -me -mm macros for troff. Which one is the most suitable? Thanks! -Tony (2 Replies)
Discussion started by: tonyt
2 Replies

2. Programming

How do capability macros get named?

The following is taken from some production code: #ifdef LOCK_LOCKF #ifdef HAVE_SYS_FILE_H #include <sys/lockf.h> #endif #ifdef HAVE_SYS_FILE_H #include <sys/file.h> #endif #define LOCK(file) fseek(file, 0L, 0), lockf(file, 1, 0L) #define UNLOCK(file) fseek(file, 0L, 0),... (2 Replies)
Discussion started by: frequency8
2 Replies

3. Programming

One last question about capability macros

This might be poorly worded. In the header file, I have #ifdef LOCK_FCNTL #ifdef HAVE_FCNTL_H #include <fcntl.h> #endif #define LOCK(file) setlock(fileno(file), F_WRLCK); #define UNLOCK(file) setlock(fileno(file), F_UNLCK); #endif /* LOCK_FCNTL */ #ifdef LOCK_FLOCK #ifdef... (1 Reply)
Discussion started by: frequency8
1 Replies

4. Shell Programming and Scripting

Expect Terminal Macros

Hey people! I just started out working at an ISP as tech support and thought that I should ease the work load by scripting some small macros. I create different commands with Alias through .bashrc which are all directed to the same script file. Here I planned on using Expect to run different... (0 Replies)
Discussion started by: GhettoFish
0 Replies

5. UNIX for Dummies Questions & Answers

MAKE and its macros and variables

I want to build a Makefile that simply takes a template file and modifies it (sed or perl, probably) before installing the result in the right place - my problem is creating the variable for substitution... So I have SYSTEM = SYS1 SYS2 SYS1_CHANNELS = CHANNEL1 CHANNEL2 CHANNEL4... (1 Reply)
Discussion started by: JerryHone
1 Replies

6. Linux

What are the meaning of these macros..

Masters, I am trying to learn the serial mouse driver for linux kernel. On the kernel source tree I find out these macros and I am unable to find out the meaning of these macros. Please anyone help me to understand these. These macros are defined in linux/serio.h... (2 Replies)
Discussion started by: iamjayanth
2 Replies

7. UNIX for Advanced & Expert Users

Using Macros in sftp command

Hi, I've some existing scripts wherein am using ftp + .netrc. I've defined my macros in .netrc file. I want to switch to sftp now but it seems it doesn't support macros and .netrc and it gives "command invalid" error. Is there any other alternative? Note: I don't want help for... (1 Reply)
Discussion started by: ps51517
1 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. Programming

help with atoi and macros in C

I have a PORT_NUM macro (10 digits long number) in a server file, if i do htons(PORT_NUM) i get warning: this decimal constant is unsigned only in ISO C90 warning: large integer implicitly truncated to unsigned type whats wrong with this? (2 Replies)
Discussion started by: omega666
2 Replies

10. Shell Programming and Scripting

Macros how-to?

Hi, all I just came to new system with RH, and it has alot of macros I was told to use, but I can't find how to open it for display or for edit, can you help me please, is it all about make/makefile? let say I have macro <trx> like this, that does a lot of things: >$ trx ... creating new... (1 Reply)
Discussion started by: trento17
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 10:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy