Sponsored Content
Top Forums Shell Programming and Scripting Enter Crtl+U character in shell script Post 302210063 by chihung on Monday 30th of June 2008 04:01:19 AM
Old 06-30-2008
It works for me. BTW, try to use vi to edit your shell script.

The sequence is:
Hold "Ctrl" key press "V"
Still holding on "Ctrl" key press "U"
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

HELP with Enter Character

I'm using PHP in my site. I have txt files for news. I reads the txt files and post the news. i have a php function that finds the caracter asc(13) which is the enter, and puts a <br>. It works in Windows, but not on Unix. Can u help me with that. Thanks (1 Reply)
Discussion started by: zecarlos
1 Replies

2. UNIX for Advanced & Expert Users

using enter key in shell script

without pressing the enter key ..manually... how can we read the enter key ..from the shell script..so that the script termintes automatically. eg: telnet a.b.c.d xxxx now " how to read the enter key" tho terminate the script (1 Reply)
Discussion started by: bishweshwar
1 Replies

3. Shell Programming and Scripting

writing Enter key inside in shell script

for automating telnet using shell script..... as we enter alphabetic characters inside shell script...how can we do the same for the enter key......Is there any character for the enter key so the enter key need not be pressed manually...... (3 Replies)
Discussion started by: bishweshwar
3 Replies

4. Linux

replacing enter character in LINUX

Hi 1) I need to replace an "enter" character with another character. I thought it should be like this (E.G) replace all stirngs "LIAV"+enter with kokokoko: :1,$s/LIAV^M/kokokoko/g but it dose not work. 2) Also dose nayone know how to replace wildcards? for... (3 Replies)
Discussion started by: liav
3 Replies

5. Shell Programming and Scripting

How to catch ENTER key inside the shell script?

Hi, I have a script in which i have to ask user to press the ENTER key to proceed further. can you please help me how can i achive this in my scripting? echo "All the executables builded Successfully " echo " Press Enter to Go Back to the Main Menu" ... (2 Replies)
Discussion started by: plaban.rout
2 Replies

6. Shell Programming and Scripting

Simulating enter key via shell script

How to simulate enter key via shell script (2 Replies)
Discussion started by: proactiveaditya
2 Replies

7. Shell Programming and Scripting

Shell Script to Enter a Directory (Folder Name Contains Spaces)

I am writing a shell script to cd to a folder. folder name is "October Scripts" I am currently storing the name of folder in a shell variable as so path="October\ Scripts/". If I do cd $path I receive the error bash: cd: October\: No such file or directory What am I doing wrong? Kindly... (3 Replies)
Discussion started by: anand2308
3 Replies

8. Shell Programming and Scripting

How to pass enter key or selected character in bash script?

hi, i've bash script thats working... but now i need to add a line....that prompts for user input....like yes and 1 as complete install.... so here's how it looks... $ cd 9200 (cd into directory) $./install (hv to type ./install to run install then ask for) ----do you want to... (4 Replies)
Discussion started by: kernel11
4 Replies

9. Shell Programming and Scripting

Search and recursively enter new line after Nth character

Hi All, My file is a string of around 50K character. I'm trying to insert new line after every 320 character in my file. I know the command to insert newline, but problem is I'm not able to search 320th position. Please advice. (6 Replies)
Discussion started by: Amit786
6 Replies

10. Shell Programming and Scripting

Shell Script for enter folders and join file

Hello everyone. I have a dlink cam that save recordings splitted for hours. Each hour folder contain a lot of small avi files. Repository has the following directories structure: \_20140101/ \_ 01 \_a.avi \_b.avi \_ 02 \_c.avi ... (3 Replies)
Discussion started by: setterx
3 Replies
LPE(1)							      General Commands Manual							    LPE(1)

NAME
lpe - Lightweight programmer's editor SYNOPSIS
lpe [ --help | --version ] lpe [--mode <mode>] [ -- ] file DESCRIPTION
Lpe is a small, fast, visual text editor designed to make editing code easier. It provides simultaneously all the features that may be required in a good code editor while preserving a light and intuitive feel that makes it nice to use. Options --help Prints a brief description of program usage and terminates. This must be the first option to lpe, and all other options are ignored. --version Prints a message indication the program version and terminates. This must be the first option to lpe, and all other options are ignored. --mode Sets the buffer mode to the one specified, instead of scanning for a suitable mode from those available. -- Treat future arguments as file names, not options. This allows lpe to be used to edit files starting with the - character. NOTES
What follows are the control key functions for lpe. Arrow keys, home, end, backspace, delete and the like all do as they would be expected to do. Some control keys are bound to the same function as some standard movement keys, such as home or page down. This is because the more intuitive keys may not be available on some systems. Command Keys Ctrl-Q Move cursor to beginning of line (alternative to Home) Ctrl-W Move cursor to end of line (alternative to End) Ctrl-R Scroll one screen up (alternative to PgUp) Ctrl-T Scroll one screen down (alternative to PgDn) Ctrl-O Move to the next word Ctrl-P Move to the previous word Ctrl-K Kill the current line Ctrl-Y or Ctrl-U Insert the most recent block of killed lines Ctrl-S Search for a specified string in the file Ctrl-A Search again for the last search query Ctrl-F Ctrl-O Open a new file to replace the current buffer Ctrl-F Ctrl-S Save the buffer to disk Ctrl-F Ctrl-A Save to disk with an alternate file name Ctrl-F Ctrl-R Read a file and insert it at the current cursor position Ctrl-F Ctrl-E Pretend that a buffer hasn't been modified Ctrl-B Ctrl-S Set the mode of the current buffer Ctrl-B Ctrl-T Toggle between hard and soft tabs for this buffer Ctrl-B Ctrl-A Toggle automatic indentation of this buffer Ctrl-G Ctrl-A Go to the first line of the buffer Ctrl-G Ctrl-S Go to the last line of the buffer Ctrl-G Ctrl-G Go to a specific line number of the buffer Ctrl-N Ctrl-R Enter a value for the command repeater Ctrl-N Ctrl-T Multiply the command repeater value by four Ctrl-N Ctrl-O Start or stop recording a macro Ctrl-N Ctrl-P Play back the last recorded macro Ctrl-V Ctrl-V Pass the entire buffer through a shell command Ctrl-V Ctrl-A Pass the entire buffer through an awk script Ctrl-V Ctrl-S Pass the entire buffer through a sed script Ctrl-V Ctrl-B Pass several lines of the buffer through a shell command Ctrl-V Ctrl-D Pass several lines of the buffer through an awk script Ctrl-V Ctrl-F Pass several lines of the buffer through a sed script Ctrl-D Perform an internal debug command Ctrl-X Write the buffer to disk and exit <interrupt> Exit without writing to disk Ctrl-Z Suspend the editor and escape to a prompt Ctrl-L Erase and redraw the entire screen <interrupt> refers to your terminal's interrupt key. This is often Ctrl-C, but can vary between terminals. Ctrl-Z, on the other hand, is fixed, regardless of the normal stop key for your terminal. MODULES
Although lpe is meant to be small, it has the capability of performing more advanced actions through a feature known as buffer modes. Buf- fer modes allow lpe to act differently according to the programming language in the current buffer. They are implemented through language modules, which are loaded at run-time by lpe to handle buffers that they apply to. All language modules should be placed in a module repository directory. These directories are set by the LPE_MODULE_PATH environment vari- able, which should be a colon-separated list of directories (similar to PATH). If this variable is not set, then lpe scans for modules in the following locations, and in this order: $HOME/.lpe /usr/local/lib/lpe /usr/lib/lpe /etc/lpe Note that the /etc/lpe directory is old, obsolete, and non-standard. It should not be used to hold modules. As modules are binary files and are specific to the architecture that uses them, they should be properly placed in the lib directories listed above. These locations are scanned at run-time, and any regular files in them are interpreted as potential language modules for use by lpe. Sub- directories will not be scanned. A buffer will be assigned the first mode found that applies to that file, so for example a mode in a user's home directory will override one in the system-wide lib directory. SEE ALSO
emacs(1), pico(1) AUTHOR
Chris Smith, cd_smith@ou.edu BUGS
Lots of 'em -- see the BUGS file in the distribution for a partial list. I am not planning on updating this man page often enough to keep up with the bug list, so I won't even try to list bugs here. 12 December 1998 LPE(1)
All times are GMT -4. The time now is 06:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy