Sponsored Content
Top Forums Programming Open Source What editor does everyone use? Post 75700 by jim mcnamara on Tuesday 21st of June 2005 01:21:19 PM
Old 06-21-2005
IMO any editor you use should have these features:
1. syntax highlighting for a variety of languages; allows creation of custom hightlighting
2. programmable (or macros)
3. support files from different platofrms (UX, DOS, etc)

vi meets some of those requirments, so it's okay in a pinch. I really like UltraEdit because it supports syntax highlighting for many dozens of languages/environments.
The bad part is it runs on Windows - I think there is an X version coming out, dunno.
This User Gave Thanks to jim mcnamara For This Post:
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Vi editor ?

Hello everybody, My question is: how to add /tmp/work at the end of line in vi editor. my file looks like: cp file1 cp file2 cp file3 **** I need to add " /tmp/work" at the end of each line. I tried this :%s/$/" /tmp/work" and this :%s/$/\ /tmp/work\/ but it does not work. (2 Replies)
Discussion started by: billy5
2 Replies

2. HP-UX

instead VI editor - which one?

I'd like to find some editor for HP-UX, something like notepad, but not VI editor. Can someone have some ideas which one? thx (6 Replies)
Discussion started by: diamond
6 Replies

3. UNIX for Advanced & Expert Users

vi editor

Hi, how can I add at the begining and at the end of all of the lines of my text file in VI editor ? Many thanks before. for exemple if in my file i have line 1 line 2 I want to have : start line 1 end start line 2 end (3 Replies)
Discussion started by: alain123456
3 Replies

4. UNIX Desktop Questions & Answers

best editor

We work on AIX 5L We use vi as text editor (only scripts to create and modifiy). What do you think of emacs ? Where can I find it ? Do you know better text editor for scripts ? Thank you for all answers. (1 Reply)
Discussion started by: annemar
1 Replies

5. HP-UX

vi editor

I am new in hp ux and I want work with vi editor, but in hp ux vi editor the backspaes and del keys doesn't work. how can I enable them. thanks (3 Replies)
Discussion started by: hkoolivand
3 Replies

6. 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

7. 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

8. Solaris

Epic Editor was not able to obtain a license for your use. Feature Epic Editor :Licen

Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down (1 Reply)
Discussion started by: durgaprasadr13
1 Replies

9. Shell Programming and Scripting

About vi editor

How can ` character be printed on vi editor ? empl_id=`echo $line | awk ' { print $1; } '` (2 Replies)
Discussion started by: senem
2 Replies

10. Shell Programming and Scripting

Not able to use @ in VI editor

Hello All, Need one Help for one issue. I am using a French Keyboard, so @ sign is on key 0 and i have to use right Alt + 0 to print it. It is working everywhere but not inside Vi editor. I can type @ in shell, in notepad. But inside Vi editor it is not working, another problem is that if... (2 Replies)
Discussion started by: yadavricky
2 Replies
LE(1)							      General Commands Manual							     LE(1)

NAME
le - full screen text editor SYNOPSIS
le [options] filename DESCRIPTION
le is a text editor which offers wide range of capabilities with a simple interface. It has a pull down menu and a simple help system to get started. See KEYS section below to learn about key combinations. Among its features there are: various operations with stream and rectangular blocks, search and replace with full regular expressions, text formatting, undelete/uninsert, hex editing, tunable key sequences, tunable colors, tunable syntax highlighting. The editor currently supports only one loaded file at a time. KEYS
Here are some starting hints: F10 or C-n menu F1 help C-x exit (cancel) Arrows navigate In the editor the following key description is used: Key1-Key2 simultaneous key1 and key2 press Key1+Key2 sequential keys press Key1 | Key2 press Key1 OR Key2 ^Key Ctrl-Key ~Key Shift-Key ^~Key Ctrl-Shift-Key | Alt-Key Some of ^Fx, ~Fx, ^~Fx can be typed as ESC+Fx. The rest of key combinations can be seen in help, in menu and in the keyboard map (default one can be seen with le --dump-keymap). There is support for block filtering through an external program, a command output read-in, writing a block through a command. To read or write block from/to a command, use F4+R or F4+W and file name of the following format: ``|command args''. Filtering is achieved by F4+| followed by command name. STATUS LINE
On the status line you can see current line, column, the size of loaded file, the code of character under cursor, several one letter flags, file name, offset in bytes from the file beginning and percent position in the file. One letters flags are: * - modified; R - Russian keyboard (works only on certain terminals); I - insert, O - overstrike; A - autoindent; D - dos style line terminators (CR NL); U - undelete possible, u - uninsert possible; B - column block mode. TEXT PROTECTION
To prevent changes loss on crash, le regularly dumps the editing text, if changed, to ~/.le/tmp/FILENAME.PID , where FILENAME is the file name with slashes converted to underlines; PID is the process id of the editor process. When the editor gets a fatal signal, it also dumps the text, to ~/.le/tmp/DUMP-SIG-FILENAME.PID , where SIG is the signal number. OPTIONS
-r, --read-only Work as viewer, don't allow changes. If your system supports mmap(2), it will be used to get file contents to memory. -h, --hex-mode Start in hex mode --mmap Use mmap(2) to load file read-only. Can be used to view very large files or even devices. This implies -h. --mmap-rw Use mmap(2) to load file read-write in MAP_SHARED mode. Use with caution -- the changes go directly to file or disk, no undo. In this mode only replace can be used, but it allows editing of very large files or even devices. This implies -h. -b, --black-white Start in black & white mode -c, --color Start in color mode --dump-keymap Dump default keymap to stdout and exit --dump-colors Dump default color map to stdout and exit --version Print the version of LE and exit --help Print short description of options and exit FILES
DATADIR/colors ~/.le/colors DATADIR/colors-$TERM ~/.le/colors-$TERM Color palette description. Those files are sequentially read and color definitions in later files have higher precision. ~/.le/keymap-$TERM DATADIR/keymap-$TERM ~/.le/keymap DATADIR/keymap Key map descriptions. Only the first existing file is read. ~/.le/term-$TERM DATADIR/term-$TERM Terminal specific options. Only the first existing file is read. Use Options->Terminal menu to tune the options. ./.le.ini ~/.le/le.ini DATADIR/le.ini Options. Only the first existing file is read. Use menu Options to tune these. .le.syntax ~/.le/syntax DATADIR/syntax Syntax highlighting rules. Only the first existing file is read. There is no default built-in in the editor, so if those files are not present you won't see any syntax highlighting. ~/.le/mainmenu DATADIR/mainmenu Main editor menu. It has simple text format. Only the first existing file is read. ~/.le/history Various histories are saved here. Do not edit by hand. DATADIR is determined at compile time by configure script (pkgdatadir variable). By default it has value /usr/local/share/le. AUTHOR
The LE editor was written by Alexander V. Lukyanov <lav@yars.free.net>. 28 Sep 2000 LE(1)
All times are GMT -4. The time now is 07:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy