× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Hello James,

I don't want to start an editor war, just wanted to bring up alternatives to already existing and perhaps not so well known editors in the i world.

Am 20.01.2023 um 17:33 schrieb James H. H. Lampert via RPG400-L <rpg400-l@xxxxxxxxxxxxxxxxxx>:

If this were a BBS instead of a list-server, I'd respond to any suggestion that vi or any vi-derivative is "easy" (especially in comparison with SEU!) with a "torrential vomiting" emoji.

I apologize. Allow me to correct my statement.

Using vim to edit already existing code is easy *for someone skilled in vi(m)*, because positional alignment can be easily gleaned from other lines.

When I'm working in Linux, from a command line, nano is my editor of choice, because at least its UI is reasonably mnemonic. But even nano is abominably clunky compared with SEU.

I wonder about your opinion. I feel the way of editing with SEU and vi quite similar. In vi you change between command and editing mode. In SEU you change positions between line numbers and text area to give editing commands. Vi(m) has no prompting facility, of course. Although I'm sure this can be programmed with vim scripts. :-) What helped me a lot was my discovery of vim syntax files on the internet, providing a colored view.

Well, I just don't like Windows and I try hard to stay away from (sometimes) bloated and slow Java applications.

To each his own.

:wq! PoC

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2023 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.