And I'm using NEdit too - since 1998.

That's what I am saying. It was more of a question of what text-editor you use because I wanted to learn all the possible choices. I didn't mean it like which text-editor should everyone use. I just wanted to see if there was a concensus. Also, there is apparently no such concensus. I would note that a great amount could give into the fact that generally it is Vim or Emacs.

You should always know how to use vi.

"vim people" will talk about how great vim is, and that's fine; I'm sure that they have innumerable reasons which they think are valid. The truth, as I see it, is that, in this day and age, unless you plan to edit text files on some old Solaris 8 machines or something, learning any variant of vi will be fine and the ability will spill over to most any other variant that you will encounter. If you want to use "advanced features" of one specific variant, then by all means learn and use them, but just plain vanilla vi has plenty of nice features in and of itself.

Once you know vi, there is really no reason to learn any other command-line text editor unless you really, really want to use some of the crazy advanced features of emacs. You will find some kind of vi clone wherever you go.

If you're like most people, then after that you can pick up and use most any X11-based editor. They are almost all the same in most respects. Try them out; you'll find that you like one of them for whatever reason and stick with it. Whichever one it is, you won't be missing much by not using any other specific one.

Personally, I find that I like 'kwrite', which comes with KDE, specifically in "Power User Mode (KDE3 Mode)". I like it because it does syntax highlighting for you, which most all of the others do as well, and also because it has a very handy "Block Selection Mode".

At the end of the day, once you're not in the command line any longer, we're just talking about GUI text editors after all ... There isn't much room for variation.

EDIT: The suggestion of using an NT-based text editor under WINE doesn't make much sense to me, but even that isn't much better or worse than anything else in X, except that maybe you'd wind up calling 'dos2unix' a lot.

Yes, I agree. If I am just copying/pasting stuff I just use the gui editor that goes with my release/desktop. I guess it is gedit, but I don't really care! As long as it does what notepad did/does, that's fine by me.

I don't think it is even a difference between "command-line" and "gui." I have an icon that starts gedit; I could just as easily have an icon to start, not an interactive shell, but a shell running vi. The only difference would be the absence of dopdown menu, so eg I have to use :w instead of mousing File->Save. Some methodology is different, that's all. vi is not really a "command-line editor," hence its name: ed, for instance, is a command-line editor --- but I think I know what you mean, which is what matters.

Those who need "portability" will indeed do well to know omnipresent vi basics. In fact, anyone who has anything at all to do with *nix probably knows the basics of vi, and if they don't they should. I often wonder at blogs and tutorials that, when giving instructions for editing config files use a command line, which might consist of a simple cat, or a complex sed. This gives no clue about the alterations in the context of the file, and worse, it leaves the inexperienced in a pickle when something goes wrong. Even with cut&paste, things can go wrong: many a time I've dropped a character, or included a unwanted punctuation --- or even found that my clipboard contained something entirely different!

Not unless you see the big difference of it among the other editors.Notepad++ works with Win, Mac and Nix file formats. You could set the default format for new files in the settings->preferences dialog box. Also, it's easy to convert one format to another via Edit->EOL Conversion.

For anyone else reading and wanting to try what he's talking about without using WINE (like a 64-bit Slackware user), Notepad+++ is an NT program that is a very close code relative of SciTE.

No real programmer ever had reason to want anything more than edlin.

I had explained enough for such kinds of answers. Not going to repeat myself again.Of course it is.And yes Scite is close since NP++ is based from Scintilla but not close enough based on capability and features.Could you elaborate? Perhaps that concludes the difference.
Or at least tell us why those are real programmers.

For anything please carefully consider my previous replies in this thread, and posts of some other people too.

Ey was joking. Look at the comic, it's making fun of the whole "real programmers do X" line of argument, each trying to outdo each other with the "spartan-ness" of their code editing method.

Yeah that last line was a joke. Hence the link to a comic strip and the suggestion that, somehow, anyone would actually be using edlin for any reason other than for nostalgia. (Edlin is what we used on DOS before edit.com was introduced.)

I never intended any disparagement of you, Notepad++, or really anything else. I'm not sure how it could have been taken otherwise, but in case it was, there you go.

Here's some backgroundinformation amongst others about edlin
the link is here

Markus

I always figured that since it was a line editor by Edwin Lingerie, the derivation of the title was quite clear ... Kindof like Linus Torvald's version of UNIX.

Sorry. I must admit I didn't read that well.

I would say it depends on what are your prospective coding tasks.

* If you just do a little occasional programming, pretty much any editor would do.

* If you intend to become a programmer, I would go either for emacs/vim, or a full-blown IDE, like eclipse. Myself, I like emacs but I have to admit that an IDE (have used netbeans for a java project) has a quite useful tools I miss in emacs.

* If you are going to do some sort of coding at customers' computers, go for something ubiquitous like vi (on unix) or wordpad/notepad (on windows -- yes, I am serious).