Sponsored Content
Top Forums UNIX for Advanced & Expert Users How to select Test in Vi Editor Post 302190761 by bakunin on Wednesday 30th of April 2008 11:55:20 AM
Old 04-30-2008
In colon-mode ("ESC", ":") enter "1,$ <your command>" to execute your command on every line between line 1 and the last line (line $). This comes as close to "selecting" a range of text in vi as is possible. In vi you "select" nothing, but use a prefix for every command to tell it which part of the file it has to work on.

I hope this helps.

bakunin
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Select ALL in VI Editor

Hi all, How can i select all and copy text in VI Editor. Rakesh Gupta (22 Replies)
Discussion started by: rakish
22 Replies

2. UNIX for Dummies Questions & Answers

Pasting text in VI editor from a different editor

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

3. Shell Programming and Scripting

set EDITOR=vi -> default editor not setting for cron tab

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

4. Shell Programming and Scripting

select some text from a test dependng on pattern

I have some absolute file location $INSTALL_BASEPATH/onereview-5.0/resources/commons-messages/commonmessages_default.properties $INSTALL_BASEPATH/onereview-5.0/orv-deploy/config-console.war/WEB-INF/classes/com/connectiva/configuration/console/resource/configurationBundle.properties I need to... (3 Replies)
Discussion started by: mnmonu
3 Replies

5. Shell Programming and Scripting

Test on string containing spacewhile test 1 -eq 1 do read a $a if test $a = quitC then break fi d

This is the code: while test 1 -eq 1 do read a $a if test $a = stop then break fi done I read a command on every loop an execute it. I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test. For example echo hello. Now the... (1 Reply)
Discussion started by: Max89
1 Replies

6. Shell Programming and Scripting

How to check weather a string is like test* or test* ot *test* in if condition

How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies

7. Shell Programming and Scripting

how to test input variable is a string in a select loop

Okay -- I hope I ask this correctly. I'm working on my little shell script to write vendor names and aliases to files from user input. If a user choose to add to a file, he can do that as well. I'm using a select loop for this function to list all the possible files the user can choose from.... (7 Replies)
Discussion started by: Straitsfan
7 Replies
EDITLINE(3)						     Library Functions Manual						       EDITLINE(3)

NAME
editline - command-line editing library with history SYNOPSIS
char * readline(prompt) char *prompt; void add_history(line) char *line; DESCRIPTION
Editline is a library that provides an line-editing interface with text recall. It is intended to be compatible with the readline library provided by the Free Software Foundation, but much smaller. The bulk of this manual page describes the user interface. The readline routine returns a line of text with the trailing newline removed. The data is returned in a buffer allocated with malloc(3), so the space should be released with free(3) when the calling program is done with it. Before accepting input from the user, the specified prompt is displayed on the terminal. The add_history routine makes a copy of the specified line and adds it to the internal history list. User Interface A program that uses this library provides a simple emacs-like editing interface to its users. A line may be edited before it is sent to the calling program by typing either control characters or escape sequences. A control character, shown as a caret followed by a letter, is typed by holding down the ``control'' key while the letter is typed. For example, ``^A'' is a control-A. An escape sequence is entered by typing the ``escape'' key followed by one or more characters. The escape key is abbreviated as ``ESC''. Note that unlike control keys, case matters in escape sequences; ``ESC F'' is not the same as ``ESC f''. An editing command may be typed anywhere on the line, not just at the beginning. In addition, a return may also be typed anywhere on the line, not just at the end. Most editing commands may be given a repeat count, n, where n is a number. To enter a repeat count, type the escape key, the number, and then the command to execute. For example, ``ESC 4 ^f'' moves forward four characters. If a command may be given a repeat count then the text ``[n]'' is given at the end of its description. The following control characters are accepted: ^A Move to the beginning of the line ^B Move left (backwards) [n] ^D Delete character [n] ^E Move to end of line ^F Move right (forwards) [n] ^G Ring the bell ^H Delete character before cursor (backspace key) [n] ^I Complete filename (tab key); see below ^J Done with line (return key) ^K Kill to end of line (or column [n]) ^L Redisplay line ^M Done with line (alternate return key) ^N Get next line from history [n] ^P Get previous line from history [n] ^R Search backward (forward if [n]) through history for text; prefixing the string with a caret (^) forces it to match only at the beginning of a history line ^T Transpose characters ^V Insert next character, even if it is an edit command ^W Wipe to the mark ^X^X Exchange current location and mark ^Y Yank back last killed text ^[ Start an escape sequence (escape key) ^]c Move forward to next character ``c'' ^? Delete character before cursor (delete key) [n] The following escape sequences are provided. ESC ^H Delete previous word (backspace key) [n] ESC DEL Delete previous word (delete key) [n] ESC ESC Show possible completions; see below ESC SP Set the mark (space key); see ^X^X and ^Y above ESC . Get the last (or [n]'th) word from previous line ESC ? Show possible completions; see below ESC < Move to start of history ESC > Move to end of history ESC b Move backward a word [n] ESC d Delete word under cursor [n] ESC f Move forward a word [n] ESC l Make word lowercase [n] ESC m Toggle if 8bit chars display as themselves or with an ``M-'' prefix ESC u Make word uppercase [n] ESC y Yank back last killed text ESC w Make area up to mark yankable ESC nn Set repeat count to the number nn ESC C Read from environment variable ``_C_'', where C is an uppercase letter The editline library has a small macro facility. If you type the escape key followed by an uppercase letter, C, then the contents of the environment variable _C_ are read in as if you had typed them at the keyboard. For example, if the variable _L_ contains the following: ^A^Kecho '^V^[[H^V^[[2J'^M Then typing ``ESC L'' will move to the beginning of the line, kill the entire line, enter the echo command needed to clear the terminal (if your terminal is like a VT-100), and send the line back to the shell. The editline library also does filename completion. Suppose the root directory has the following files in it: bin vmunix core vmunix.old If you type ``rm /v'' and then the tab key. Editline will then finish off as much of the name as possible by adding ``munix''. Because the name is not unique, it will then beep. If you type the escape key followed by either a question mark or another escape, it will dis- play the two choices. If you then type a period and a tab, the library will finish off the filename for you: rm /v[TAB]munix.[TAB]old The tab key is shown by ``[TAB]'' and the automatically-entered text is shown in italics. BUGS AND LIMITATIONS
Cannot handle lines more than 80 columns. AUTHORS
Simmule R. Turner <uunet.uu.net!capitol!sysgo!simmy> and Rich $alz <rsalz@osf.org>. Original manual page by DaviD W. Sanderson <dws@ssec.wisc.edu>. EDITLINE(3)
All times are GMT -4. The time now is 01:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy