>>> and for compiling core java programme you can use Textpad software.
>>>
[quoted text clipped - 17 lines]
>
> I am using JEdit today.

Signature
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |
>>>> and for compiling core java programme you can use Textpad software.
>>>>
[quoted text clipped - 24 lines]
> microEmacs on Fedora or Microware's OS-9. Theres a decent Windows port
> of microEmacs too, though its probably not to everybody's taste.
For Java, I almost never use anything but Eclipse.
Otherwise, on Windows, I tend to use SciTE for Ruby. Otherwise, I
generally use EMEditor, because it has full programmable macros. But I
keep TextPad as a backup, since it can edit hex data.
When my ThinkPad was in the shop, and I had to use my wife's Mac for a
while, I tried JEdit, but it seemed unnatural. vi (which I was familiar
with from Irix) kept making trouble because of LF/CRLF issues. I really
don't know what I'm going to do when (as I plan) I switch to a Mac,
myself -- probably start huntine up Eclipse extensions.
In many ways, I miss IBM's epm (for OS/2), especially the downloadable
enhanced version that included the source code and compiler. (It was
coded in a special language called E.)

Signature
John W. Kennedy
"The blind rulers of Logres
Nourished the land on a fallacy of rational virtue."
-- Charles Williams. "Taliessin through Logres: Prelude"
Lew - 23 Feb 2007 22:47 GMT
> For Java, I almost never use anything but Eclipse.
For Java, I use whatever the employer demands, but if they don't make demands,
I use Netbeans. Mostly - my alternative is emacs.
"Editor wars" <http://en.wikipedia.org/wiki/Editor_wars> have been around for
a really long time.
- Lew
Martin Gregorie - 24 Feb 2007 15:09 GMT
> When my ThinkPad was in the shop, and I had to use my wife's Mac for a
> while, I tried JEdit, but it seemed unnatural. vi (which I was familiar
> with from Irix) kept making trouble because of LF/CRLF issues. I really
> don't know what I'm going to do when (as I plan) I switch to a Mac,
> myself -- probably start huntine up Eclipse extensions.
Its always good to know vi because it works with minimal display
capabilities and doesn't require much from the keyboard - not even arrow
keys are needed, which is handy if you're really stuck with a bad
termcap or terminfo definition. I've yet to see a *nix that doesn't have
a version installed.
OS X probably uses the vim flavor of vi. Its the standard version on
Linux these days. Its has various improvements over the original and is
pretty good as far as vi clones go - certainly better IMO that stevie or
elvis. To complete the picture, I rather like pvic. This is a minimal vi
clone that's written in pure C. I've used it with OS-9 and DOS.

Signature
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |
Ed Jensen - 24 Feb 2007 23:17 GMT
> vi (which I was familiar > with from Irix) kept making trouble
> because of LF/CRLF issues.
VIM (Vi IMproved) and GVIM (Graphical VIM) can recognize the newline
sequence used by the file you're editing and adjust themselves
automagically.
JussiJ - 28 Feb 2007 23:27 GMT
> Otherwise, I generally use EMEditor, because it has full
> programmable macros.
FWIW Zeus is also fully scriptable:
http://www.zeusedit.com
In fact Zeus scripts can be written in Lua, Python, TCL,
Java Script, VB Script or Ruby ;)
Jussi Jumppanen
Author: Zeus for Windows IDE