Sponsored Content
Full Discussion: Lost pico editor
Top Forums UNIX for Dummies Questions & Answers Lost pico editor Post 302068735 by zazzybob on Monday 20th of March 2006 08:20:43 PM
Old 03-20-2006
Reinstall pico....

Before you do that, try

find / -name "pico" -print

Just to rule out the possibility that it hasn't been moved, it's not in your $PATH, etc.

Then, either install from your installation media, or download.

Cheers
ZB
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

vi and pico

hello iam so new to unix / apache what is the dif between VI and PICO where can i get hands on training with both in Los Angeles any ideas would be helpfull. thanx whothought (5 Replies)
Discussion started by: whothought
5 Replies

2. UNIX for Dummies Questions & Answers

pico text editor

I was wondering if there is any way to get a version of pico for windows. I have done a lot of programming work on Linux/UNIX exvironments for school, and I enjoy using pico for my programming needs, but I find all of the text editors in windows horrible, they distort my code and do not adhere to... (5 Replies)
Discussion started by: popac
5 Replies

3. UNIX for Dummies Questions & Answers

question about pico?

Quick question for all of you Unix gurus. What are your thoughts on Pico as an editor. I have been using this editor for the last week or so and have made a lot of headway with my script writing. However, I find a lot of the quirks associated with this editor to be quite annoying. For instance,... (1 Reply)
Discussion started by: wmosley2
1 Replies

4. UNIX for Dummies Questions & Answers

How to load text editor PICO

Hi... I was wondering if anyone has any step by step guide on how to load the UNIX text editor PICO onto the Sun box? Thanks :) (2 Replies)
Discussion started by: atomicsushi
2 Replies

5. UNIX for Dummies Questions & Answers

Pico?

Is pico editor not availible on all versions of Unix? I do have vi and emacs, but pico just give me a response of "not found". (4 Replies)
Discussion started by: dereckbc
4 Replies

6. UNIX for Dummies Questions & Answers

Can't run emacs, pico..

Hello, I cannot run emacs or pico from my Sun OS command shell. My account does not have a .cshrc file also. When I tried to make a text file and copied it to my account by the name .cshrc, the source commands I place in it do not work. Can anybody tell me how can I solve this? Any help... (8 Replies)
Discussion started by: aryajur
8 Replies

7. Filesystems, Disks and Memory

Lost Data Lost Admin

First time so excuse my ignorance please. I may not be accurately describing the issue. I have inherited a small lab mostly SUN V120s. We lost power and are trying to recover. Nope no backups... The primary issue I have is 1 box is an Oracle Server. It has 2 36Gb harddrives. I am able to... (3 Replies)
Discussion started by: murphsr
3 Replies

8. UNIX for Dummies Questions & Answers

pico vs vim

I always used pico as a text editor in Terminal or SSH. But what is the advantages/disadvantages between vim and pico? (7 Replies)
Discussion started by: timgolding
7 Replies

9. UNIX for Dummies Questions & Answers

Ed vs pico

Hello! Please, can someone make me clear the difference betveen and interactive and non-interactive test editor? (is not each editor somehow "interactive"???) Many thanks!!! (0 Replies)
Discussion started by: pinklemon
0 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 11:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy