Sponsored Content
Top Forums Shell Programming and Scripting Any shell or hack that makes the shell command line take vi commands? Post 302649065 by marqul on Wednesday 30th of May 2012 08:10:05 PM
Old 05-30-2012
Any shell or hack that makes the shell command line take vi commands?

basically i'm tired of hitting the left arrow a few dozen times when correcting a mistake or modifying a history command

i'd like to use vim style key shortcuts while on the command line so that a 55[left arrow key] moves the cursor 55 places to the left...

and i want all the other vi goodies, search of history maybe - a dream?, replace, etc
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

KORN Shell - Spawn new shell with commands

I want to be able to run a script on one server, that will spawn another shell which runs some commands on another server.. I have seen some code that may help - but I cant get it working as below: spawn /usr/bin/ksh send "telnet x <port_no>\r" expect "Enter command: " send "LOGIN:x:x;... (2 Replies)
Discussion started by: frustrated1
2 Replies

2. Shell Programming and Scripting

How to run unix commands in a new shell inside a shell script?

Hi , I am having one situation in which I need to run some simple unix commands after doing "chroot" command in a shell script. Which in turn creates a new shell. So scenario is that - I need to have one shell script which is ran as a part of crontab - in this shell script I need to do a... (2 Replies)
Discussion started by: hkapil
2 Replies

3. UNIX for Dummies Questions & Answers

what are some different commands in c shell and korn shell??

I am doing this simple script using c shell and korn shell. The commands I use are fgrep , ls, and also some redirecting. Is there any difference in using both of these commands in c shell and korn shell? Thanks and sorry for the stupid question. (1 Reply)
Discussion started by: EquinoX
1 Replies

4. Shell Programming and Scripting

Can BASH execute commands on a remote server when the commands are embedded in shell

I want to log into a remote server transfer over a new config and then backup the existing config, replace with the new config. I am not sure if I can do this with BASH scripting. I have set up password less login by adding my public key to authorized_keys file, it works. I am a little... (1 Reply)
Discussion started by: bash_in_my_head
1 Replies

5. UNIX for Dummies Questions & Answers

Passing command line argument between shell's

Hi, I am facing a problem to pass command line arguments that looks like <script name> aa bb "cc" dd "ee" I want to pass all 5 elements include the " (brackets). when I print the @ARGV the " disappear. I hope I explain myself Regards, Ziv (4 Replies)
Discussion started by: zivsegal
4 Replies

6. UNIX for Dummies Questions & Answers

Command line ok but not shell

I want to substitute a charactor "PAN" with "TAN" in a shell, I used sed command in shell, it wo'nt work but the same is run from command prompt it was successful. the command is sed ' s/PAN/TAN/g ' <i/p> > <o/p> sed ' s/^M/^M/g ' <i/p> > <o/p> (1st ^M is Ctrl+V+M, 2nd should be line feed/next... (2 Replies)
Discussion started by: anil_kut
2 Replies

7. Shell Programming and Scripting

Shell Text Based Game, This Error Makes NO sense. Please help

Okay so I'm making a simple text based game that branches into different scenarios. By branching I mean branching off into whole different files with that part of the game in it. I got tired of working on scenario 1 so I'm working on scenario 2. As I get started and try to test it, I get an... (3 Replies)
Discussion started by: lemonoid
3 Replies

8. Shell Programming and Scripting

Embeded shell variable in command line

Hello, I know this is a situation about the single quote and double literal, but I could not figure out after many search. I need to loop through thousands of different BACs sequencing to optimize kmer individually. IN=/PATH/TO/INPUT/FILES for sample in S{01..1096} do run_program... (9 Replies)
Discussion started by: yifangt
9 Replies

9. UNIX for Dummies Questions & Answers

Ls -1 at Command Line vs in a Shell Script

Hello, I have symbolic links to a bunch of directories (all starting with the letter X) in the cwd. When I run the following on the command line, I get the list as I want it. ls -1 X* > dir.list However when I run it in a shell script like given below, it lists all the files in each of... (3 Replies)
Discussion started by: Gussifinknottle
3 Replies

10. Shell Programming and Scripting

Need help with shell commands (not sure which command is appropriate)

Dear All, I have 2 files namely file1 and file2. in file1 I have something like this Min X = -250.000000, Max X = 250.000000 Min Y = -95.000000, Max Y = 95.000000 Min Z = -95.000000, Max Z = 136.500000 I have to write this date to file2 as xMin -250.000000; xMax 250.000000; yMin... (15 Replies)
Discussion started by: linuxUser_
15 Replies
LEDIT(1)						      General Commands Manual							  LEDIT(1)

NAME
ledit - line editor, version 2.03 SYNOPSIS
ledit [-h file] [-x] [-t] [-l length] [-a | -u] [command options] DESCRIPTION
The command ledit allows to edit lines one by one when running an interactive command. When typing a line, some keys with control or meta are interpreted: it is possible to insert characters in the middle of the line, go to the beginning or the end of the line, get a previous line, search for a line with a pattern, etc. OPTIONS
The options are: -h file Save the lines typed (history) in file. The default is to have them only in memory (so, they are lost at the end of the program). -x Extend the history file (given in option "-h") if it already exists. The default is to truncate the history file. -t Display the sequences generated by the keys (for debugging). -v Print ledit version and exit. -l length Tells that length is the maximum line length displayed. If the line edited is longer than this length, the line scrolls horizon- tally, while editing. The default value is 70. -a Ascii encoding: characters whose code is greater than 128 are displayed with a backslash followed by their code. -u Unicode encoding: the terminal must have been set in unicode mode. See commands unicode_start and unicode_stop. command options Runs the command command and its possible options. This must be the last option of ledit. The default value is "cat". KEYS BINDINGS
When ledit starts, some default key bindings are defined. The can be completed with a "leditrc" file. See the section LEDITRC. In the following lines, the caret sign "^" means "control" and the sequence "M-" means "meta" (either with the "meta" prefix, or by press- ing the "escape" key before). Examples: ^a press the "control" key, then press "a", then release "a", then release "control". M-a press the "meta" key, then press "a", then release "a", then release "meta", or: press and release the "escape" key, then press and release "a" (the manipulation with "meta" may not work in some systems: in this case, use the manipulation with "escape"). The default editing commands are: ^a : beginning of line ^e : end of line ^f : forward char ^b : backward char M-f : forward word M-b : backard word TAB : complete file name ^p : previous line in history ^n : next line in history M-< : first line in history M-> : last line in history ^r : reverse search in history (see below) ^d : delete char (or EOF if the line is empty) ^h : (or backspace) backward delete char ^t : transpose chars M-c : capitalize word M-u : upcase word M-l : downcase word M-d : kill word M-^h : (or M-del or M-backspace) backward kill word ^q : insert next char M-/ : expand abbreviation ^k : cut until end of line ^y : paste ^u : line discard ^l : redraw current line ^g : abort prefix ^c : interrupt ^z : suspend ^ : quit return : send line ^x : send line and show next history line other : insert char The arrow keys can be used, providing your keyword returns standard key sequences: up arrow : previous line in history down arrow : next line in history right arrow : forward char left arrow : backward char Other keys: home : beginning of line end : end of line delete : delete char page up : previous line in history page down : next line in history shift home : beginning of history shift end : end of history REVERSE SEARCH
The reverse search in incremental, i.e. ledit backward searchs in the history a line holding the characters typed. If you type "a", its search the first line before the current line holding an "a" and displays it. If you then type a "b", its search a line holding "ab", and so on. If you type ^h (or backspace), it returns to the previous line found. To cancel the search, type ^g. To find another line before holding the same string, type ^r. To stop the editing and display the current line found, type "escape" (other commands of the normal editing, different from ^h, ^g, and ^r stop the editing too). Summary of reverse search commands: ^g : abort search ^r : search previous same pattern ^h : (or backspace) search without the last char del : search without the last char any other command : stop search and show the line found LEDITRC
If the environment variable LEDITRC is set, it contains the name of the leditrc file. Otherwise it is the file named ".leditrc" in user's home directory. When starting, ledit reads this file, if it exists, to modify or complete the default bindings. If this file is changed while reading lines, it is read again to take the new file into account. Bindings lines are the ones which start with a string defining the key sequence and follow with a colon and a binding. A binding is either a string or a command. The other lines are ignored For example,the line: "C-a": beginning-of-line binds the sequence "control-a" to the command "beginning-of-line". The key sequence may contain the specific meta-sequences: C- followed by a key: "control" of this key M- followed by a key: "meta" of this key e the "escape" key nn where nnn is one, two, or three octal digits, or: xnn where nn is one or two hexadecimal digits: the binary representation of a byte a bell = C-g  backspace = C-h d delete = 277 f form feed = C-l newline = C-j carriage return = C-m tabulation = C-i v vertical tabulation = C-k The commands are: abort: do nothing accept-line: send the current line backward-char: move the cursor to the previous character backward-delete-char: delete the previous character backward-kill-word: delete the previous word backward-word: move the cursor before the previous word beginning-of-history: display the first line of the history beginning-of-line: move the cursor at the beginning of the line capitalize-word: uppercase the first char and lowercase the rest delete-char: delete the character under the cursor delete-char-or-end-of-file: same but eof if no character in the line downcase-word: lowercase whole word end-of-history: display the last line of the history end-of-line: move the cursor to the end of the line expand-abbrev: try to complete the word by looking at the history expand-to-file-name: try to complete the word from a file name forward-char: move the cursor after the next word forward-word: move the cursor to the next character interrupt: interrupt command (send control-C) kill-line: delete from the cursor to the end and save in buffer kill-word: delete the next word next-history: display the next line of the history operate-and-get-next: send line and display the next history line previous-history: display the previous line of the history quit: quit ledit quoted-insert: insert the next character as it is redraw-current-line: redisplay the current line reverse-search-history: backward search in the history suspend: suspend ledit (send control-Z) transpose-chars: exchange the last two characters unix-line-discard: kill current line upcase-word: uppercase whole word yank: insert kill buffer KNOWN BUGS
If ledit has been launched in a shell script, the suspend command kills it and its command... Use "exec ledit comm" instead of "ledit comm". The suspend command stops ledit but not the called program. Do not do this if the called program is not waiting on standard input. In some systems (e.g. alpha), pasting two many characters works bad and may block the terminal. Probably a kernel problem. No solution. SEE ALSO
unicode_start(1), unicode_stop(1). AUTHOR
Daniel de Rauglaudre, at INRIA, france. daniel.de_rauglaudre@inria.fr INRIA
Wed Jan 23, 2008 LEDIT(1)
All times are GMT -4. The time now is 12:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy