Sponsored Content
Full Discussion: Stupid question
Top Forums UNIX for Dummies Questions & Answers Stupid question Post 302216633 by reborg on Sunday 20th of July 2008 04:56:15 PM
Old 07-20-2008
Most commands can be interrupted with a Ctrl+c.

Otherwise you can used Ctrl+z to suspend the process and then kill it from the bash command line.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Stupid Question?

I have a SparcStation 10 and it came with an external CD Rom Drive. I am trying to install Solaris 2.6 Server on this machine from the Cd Rom. At the OK> prompt I type "boot cdrom - browser" and I get an error: scsi device not found:error = -1 or something to that effect. Does anyone have any... (9 Replies)
Discussion started by: jskillet
9 Replies

2. UNIX for Dummies Questions & Answers

Stupid question...

Hello, I've always been around systems that ran windows in one version or another, so I'm familiar with what/when/where/drivers/etc for that. I want to build a unix box to use as a place to learn and become more familiar with unix. I would also like to eventually convert it to a server to... (6 Replies)
Discussion started by: Cortney
6 Replies

3. UNIX for Dummies Questions & Answers

sorry if this is a stupid question

Hi All, just a thought is it possible to make the shell read the following command $ $*pdf to list all pdf ($ls *.pdf) and $*htm as ($ls *.htm) Thanks for the inputs :) (2 Replies)
Discussion started by: sskb
2 Replies

4. UNIX for Dummies Questions & Answers

Stupid question

I need to convert a Unix file to a 'Dos' file. Ie if I look at the converted file in 'vi' on Unix it will have '^M' at the end of each line. Hopefully it won't be a case of reading each line in turn and adding a \n. I've heard there is some sort of unix2dos command but it is not recognised on... (2 Replies)
Discussion started by: Bab00shka
2 Replies

5. UNIX for Dummies Questions & Answers

stupid question!?

fedora core 2 xx8. 5xx version (not sure! not sure how to look it up either..(except on boot sorry!!)).. :( the linux version I started on last year was an old redhet 6.0 version with only text mode.. back then for some reason I knew I how to get rid of whole directories without a) going through... (6 Replies)
Discussion started by: moxxx68
6 Replies

6. UNIX for Dummies Questions & Answers

Sorry! Stupid question, but...

Hey everybody. I'm going through my system (Mac OS X 10.3.9, through the Terminal application) trying to get rid of instances of MySQL that I installed over each other. I was having trouble getting MySQL to work: it wasn't letting me set the password, then it wouldn't let me create new databases... (2 Replies)
Discussion started by: starscream
2 Replies

7. IP Networking

stupid IP question

Hello! I'm sorry - I know nothing about computers, but I have a dumb question. Could someone explain to me if two computers, say in a large city, could have the same IP address on different days, if they were using broadband internet? Or, is it possible an internet service provider could assign... (3 Replies)
Discussion started by: sugarsweet
3 Replies

8. UNIX for Dummies Questions & Answers

One stupid question

Has anybody come across the situation when after openning the cover of HP9000 the PC will not start. We checked everything but did not manage to find any solution to that. The PS seems to be functionning (at lease we can hear it clicking). Please help us solving the problem. Thanks to everybody. (2 Replies)
Discussion started by: Andrey Malishev
2 Replies

9. UNIX for Dummies Questions & Answers

Stupid question

Hi all, Please excuse my ignorance - I'm a Cisco kid and my knowledge of Unix is somewhat flaky!! Basically we're running MRTG on an HP-UX server and wondered what the "-" means in the following text within the crontab file - -* * * * * root /home/mrtg/fwdev01.sh I... (3 Replies)
Discussion started by: freakydancer
3 Replies

10. AIX

stupid question: the path

I'm sorry for my stupid question, but when I log in with one account on my AIX machine, I see: psar3@caixpc24: /home/psar3 > > When I login with another login (pger1), I see: caixpc24 # how can i change that i see the same for pger1 as for psar3??? (it's easy to see with which... (4 Replies)
Discussion started by: Leilah
4 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 02:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy