One thing I miss from the Prime editor is overlay. All you had to do is
space out to where you wanted to overly the text and overlay with the new
characters. It was very useful when you had a long string with several
instances of the same type of information and you only wanted to change one
area.
Example:
DATA = 'AAABBBCCCAAABBBCCCAAABBBCCC'
O ZZZ
DATA = 'AAABBBCCCAAABBBCCCZZZBBBCCC'
Sure beat having to type the whole line or doing a long change.
----- Original Message -----
From: "Warren, Phil" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 23, 2004 2:24 PM
Subject: RE: [U2] Comparison Unidata and Universe
As a system administrator, my choice is to use vi for my UNIX/AIX duties,
but I find it's quite a useful tool for program editing too. In fact, I'm
the only one in our shop that uses vi on a regular basis. I still can't
figure out why the remainder of our programming staff use AE. I agree it
has it's place for some tasks, but for day to day editing, I find vi easy to
use, and it didn't take too long to get used to, when I learned it years
ago. The best part is that you'll find it on most flavors of UNIX boxes,
and the basic commands stay the same. -Phil-
-----Original Message-----
From: Louis Guillaume [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 22, 2004 7:52 PM
To: [EMAIL PROTECTED]
Subject: Re: [U2] Comparison Unidata and Universe
Adrian Matthews wrote:
> Does anyone actually use the editor for cutting code these days though?
>
Absolutely! From what I've seen, most folks who take the time to learn
vi will never go back.
The only thing AE is good for is macro-fixing savedlists of records,
IMHO. It really astonishes me that folks continue to use AE for editing
programs where you can really only look at one line at a time.
> I've been using full screen GUI editors for years now. I think I'd pull
> my hair out going back.
GUI editors generally lack many of the vi features: use of regular
expressions, superior cut and paste, multiple cut/paste buffers, the
ability to read the output of external commands into the file, the
ability to employ Unix shell utilities (like sed or awk) to edit the
file etc etc.
The only GUI editor I'd use for programming is vim! It is absolutely
worth it to learn vi or vim for editing in UniData (and, I'm sure
UniVerse too). If you're on Windows, there's Vim for Windows.
I don't know much about UniVerse, but I can't imagine that an editor
should make any difference as most editors should be available to either
platform. On UniData just set the variable UDT_EDIT=/usr/local/bin/vim
(or whatever your editor is) and voila.
-- Louis
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
