Favourite Linux Text Editor?

[crokett]

The Linux Experiement has begun!
\
I got a 2nd machine at work and installed my company's version of Linux - basically a base distro with custom desktop and some other business required SW. I got my email and chat moved over today. Much of what I do is web-based but I really need a text editor. I love PSPad in Windows but there is not a *nix version. I need one that will

a) handle multiple large files - up to 30 MB in size (each) - in tabs
b) support backwards/forwards/global searches
c) support bookmarking once I find something
d)syntax highlighting, preferably that I can customize

[kirkroy]

Run PSPad inside WINE if you don't want to learn something new...

[dbhost]

The Linux Experiement has begun!
\
I got a 2nd machine at work and installed my company's version of Linux - basically a base distro with custom desktop and some other business required SW. I got my email and chat moved over today. Much of what I do is web-based but I really need a text editor. I love PSPad in Windows but there is not a *nix version. I need one that will

a) handle multiple large files - up to 30 MB in size (each) - in tabs
b) support backwards/forwards/global searches
c) support bookmarking once I find something
d)syntax highlighting, preferably that I can customize

I was going to say VI, but uh... dang...

Okay what about vim-X11. Not sure if it supports what you are looking for, but I know our developers use the snot out of it...

I work mostly CLI when using text editors...

[radhak]

a) handle multiple large files - up to 30 MB in size (each) - in tabs
b) support backwards/forwards/global searches
c) support bookmarking once I find something
d)syntax highlighting, preferably that I can customize

Seems like specs for Vim . Does all that and more. If you have not used it, highly recommend it.

In fact, recommend vim for all platforms, as there are versions for anything you might be using, check this page : http://www.vim.org/download.php. I even use gvim for windows at work (the g indicates gui or graphical interface, ie, word-like instead of the classic vi-like), and nothing beats it.

[cbrown]

Once you've used vi, you'll never go back to ed. . .

If it can't be done in vi, t'aint worth doing. . .

I can still feel the commands in my fingers!

Chris

[sd]

I think Kate has all the features you mentioned. But, for the ultimate in editors, there is a
Linux version of Teco. All you need is one of these.

[DaveS]

I agree - use vim - be productive.

Learning vim will enable you to edit on any *nix you run across.

Do a google on "vim cheat sheet pdf" and you will find a bunch of handy sheets to print out and put next to your keyboard while you are learning.

If you must have a gui editor, then at least use elvis. But honestly, once you get good at vi, you will never take your hands off the keyboard - you will wonder how you ever used such a clunky interface in an editor that requires you to use a [yeech] mouse.

While we are at it: "SPACES!"

:wq!

[DaveS]

Once you've used vi, you'll never go back to ed. . .

If it can't be done in vi, t'aint worth doing. . .

I can still feel the commands in my fingers!

Chris

Sing it, brother! Amen!

[BobSch]

Real men do typsetting with just vi, nroff and troff.

(At least we did twenty years ago.)

[sparkeyjames]

Jed when using a command line. Small footprint. Emacs like command keys. Fairly configurable. I have been using it for so long now other editors feel clunky. KDE's Kate when using the GUI. For office type stuff I use Openoffice.

[ejpotter]

Definitely another vote for vim! There's a pretty steep learning curve, but once you begin to get the sense of it... wow! Incredibly fast, customizable syntax highlighting for just about every language imaginable, get a gui version such as gvim and you've got tabs... if you take the time to learn it, you'll never go back to anything else. Everything can be done from the keyboard, pretty much w/o ever taking your fingers off the base keys. I find myself trying to use vim-ingrained keyboard sequences to edit in gmail and openoffice when I have to use it for some reason.

[crokett]

I used vi a fair bit once upon a time and hated it. Still do. Besides which most of my other work is with GUI programs (lots of cut n paste) so I'd rather not keep having to take my hands off a mouse.

I will need either Wine or a virtual machine of some sort eventually so I could (and may) stay with PSPad but I'd prefer a native app. I have 2 critical pieces of SW that I don't use all that much but they are Windows only.

Hrrm... now I'm embarrassed as it appears gedit may do what I want. I will work with it tomorrow see how it goes.

I will also take a look at elvis.

[radhak]

I get your issues with vi, no arguments, and that's why i suggested gvim.

It is exactly as gui as any another windows app, all with the mouse : copy, paste, and what-not.

I'd even stick my neck out and claim that for basic editing, the learning curve can be pretty small, particularly if you have used vi before.

<Now going a bit tangential to the original post>

Of course the beauty of vim is when the going gets tough :
as an example, if you have this text (from a create table command):

Shape varchar (20) ,
Color varchar (20) ,
Clarity varchar (20),
Symmetry varchar (20) ,
Polish varchar (20) ,
Report varchar (20) ,
Girdle varchar (20) ,
Florescence varchar (20) ,

and you want to make an SQL assign out of it, like this:

,Shape = D.Shape
,Color = D.Color
,Clarity = D.Clarity
,Symmetry = D.Symmetry
,Polish = D.Polish
,Report = D.Report
,Girdle = D.Girdle
,Florescence = D.Florescence

a single line command does it :

%s/\(\w\+\)\s\+.*/,\1 = D.\1/

I'm not sure which other editor will do it with as much ease.

[crokett]

I get your issues with vi, no arguments, and that's why i suggested gvim.

Sorry. I read your post and got the impression gvim was for Windows. I will check it out too.

The quote function doesn't quote code, but I am still enough of a geek to laugh at the 'single command'.

[gerti]

Never could get used to vim etc, I want my mouse. I used jEdit for quite some time, though I don't know how it does on very big files: http://jedit.org/