08-17-2008
perl colors in nedit editor
Hi,
I would like to change the color of the nedit editor for perl scripts.
I tried to find the .nedit file in my $HOME directory but didn't find it.
Can anyone tell where can I find the .nedit file or where can I modify the
color for perl scripts in the nedit editor ?
Thanks in advance
9 More Discussions You Might Find Interesting
1. HP-UX
hi
1).in the command "set" result, the 2nd line is
EDITOR=vi
is it means the vi editor is the default editor?
2). is "nedit"editor available in hpux 11iv2?
if no how to install or work in nedit in hpux 11i? (0 Replies)
Discussion started by: sekar sundaram
0 Replies
2. UNIX for Dummies Questions & Answers
Hello,
My System Admin. just switched me from KSH to BASH and something happened to my "nedit" utility!
Does anyone know how to reactivate nedit by anychance?
Thanks very much!
BobK (2 Replies)
Discussion started by: bobk544
2 Replies
3. Shell Programming and Scripting
Hi,
I saw some people's vi editor show different colors on the text according the nature of text when using it.
It would be nice if I can see diffrerent colors with my vi editor.
Do anybody know how to set it up?
I use PowerTermPro program to access unix machine.
I tried to use vim editor but... (7 Replies)
Discussion started by: whatisthis
7 Replies
4. UNIX for Dummies Questions & Answers
I have only slight difference between remarks (gray) and code (black)
using c and c++ how cani change remark to other color ?
The option preferences/language mode/c++ doesn't help (0 Replies)
Discussion started by: eynkesef
0 Replies
5. UNIX for Dummies Questions & Answers
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
6. Shell Programming and Scripting
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
7. Shell Programming and Scripting
Hi Perl folks,
I am having problems printing elements from an array at runtime.
I wish to push elements into array at runtime and the print it later.
Now I wish to print this matrix using colors.
So I do something like this to enter the runtime values in array:
... (1 Reply)
Discussion started by: som.nitk
1 Replies
8. Programming
i have following code that runs fine on my Ubuntu workstation. However when i run this on a HPUX it wont open the text file i am trying to open for editing. I figured i just have to change gvim editor to vi, but that didnt work out well. Can some one help me out here? This is written in Perl
... (1 Reply)
Discussion started by: usustarr
1 Replies
9. Shell Programming and Scripting
Dear Help,
I have been encountering a strange problem.
When I run a shell script, I do expect the output number of lines to be 12000 and it runs fine on one my linux w/s.But it just terminate at line 2704 on another linux machine.
I have put 'nedit text.file' at the last part of the script,... (5 Replies)
Discussion started by: Indra2011
5 Replies
EX(1) General Commands Manual EX(1)
NAME
ex, edit - text editor
SYNOPSIS
ex [ - ] [ -v ] [ -t tag ] [ -r ] [ +command ] [ -l ] name ...
edit [ ex options ]
DESCRIPTION
Ex is the root of a family of editors: edit, ex and vi. Ex is a superset of ed, with the most notable extension being a display editing
facility. Display based editing is the focus of vi.
If you have not used ed, or are a casual user, you will find that the editor edit is convenient for you. It avoids some of the complexi-
ties of ex used mostly by systems programmers and persons very familiar with ed.
If you have a CRT terminal, you may wish to use a display based editor; in this case see vi(1), which is a command which focuses on the
display editing portion of ex.
DOCUMENTATION
The document Edit: A tutorial (USD:14) provides a comprehensive introduction to edit assuming no previous knowledge of computers or the
UNIX system.
The Ex Reference Manual - Version 3.7 (USD:16) is a comprehensive and complete manual for the command mode features of ex, but you cannot
learn to use the editor by reading it. For an introduction to more advanced forms of editing using the command mode of ex see the editing
documents written by Brian Kernighan for the editor ed; the material in the introductory and advanced documents works also with ex.
An Introduction to Display Editing with Vi (USD:15) introduces the display editor vi and provides reference material on vi. In addition,
the Vi Quick Reference card summarizes the commands of vi in a useful, functional way, and is useful with the Introduction.
FILES
/usr/share/misc/exstrings error messages
/usr/libexec/exrecover recover command
/usr/sbin/expreserve preserve command
/etc/termcap describes capabilities of terminals
~/.exrc editor startup file
/tmp/Exnnnnn editor temporary
/tmp/Rxnnnnn named buffer temporary
/usr/preserve preservation directory
SEE ALSO
awk(1), ed(1), grep(1), sed(1), grep(1), vi(1), termcap(5), environ(7)
AUTHOR
Originally written by William Joy
Mark Horton has maintained the editor since version 2.7, adding macros, support for many unusual terminals, and other features such as word
abbreviation mode.
BUGS
The undo command causes all marks to be lost on lines changed and then restored if the marked lines were changed.
Undo never clears the buffer modified condition.
The z command prints a number of logical rather than physical lines. More than a screen full of output may result if long lines are
present.
File input/output errors don't print a name if the command line `-' option is used.
There is no easy way to do a single scan ignoring case.
The editor does not warn if text is placed in named buffers and not used before exiting the editor.
Null characters are discarded in input files, and cannot appear in resultant files.
4th Berkeley Distribution October 21, 1996 EX(1)