Good text/code editor

Hey
What's a good code/text editor? Something like notepad but that highlights html code, strings etc. And I don't want it to choke on big files like notepad does...

emacs

vim

thanks

Pico

textpad

zile

mycock

Crimson Editor

cat (and netcat for the internet)

SubEthaEdit

>>1

I love SlickEdit. It's completely customizable, it really is a text editor for programmers who just need a text editor.

Costs money though, but I am not regretting my investment one bit. You can even code the interface to do whatever you want. Supports regex too I think, so you can potentially do some really powerful things.

>>12

Temptation to flame my way into an editor holy war... rising...

ED

ED is the standard text editor.

I always though pico was today's standard text editor.
They're all fairly similar in simplicity anyway.

>>11
Subethatedit is indeed a very, very cool editor with many features, including the very cool network editing one. However it's OS X only, is it not? It's fine for me, but I doubt it interests everyone here. Not a bad idea mentioning it though.

I use nano (or pico, I forget which) mostly when I want to paste in a bunch of code I found on a webpage or something and I don't want vim to mess it up by autoindenting. For actually editing I use vim. I believe it was actually voted best editor by... someone... according to the web site.

ED, ED, ED! ED GIVES YOU STRENGTH! STRENGTH CRUSHES ENEMIES! ED!

I think my ed is broken. I fired it up and... well here:

[jesus@neonatix ~]$ ed
hello
?
what
?
read my input bitch
?
^[[A
?

?

Ah, good old ed

Actually I wanted Windows editors, but never mind I got Cream and it seems good.

CoffeeCup
Textpad
VI

>>21

gvim

ConText is under Windows

I would say for Windows you could search around for commerical applications or freeware that suite your needs well enough.. How ever it would really be worth it to grab gvim or xemacs and learn how to use them.. It will help you use anything in the long run.. Plus the amount of scriptability/customizability of the editors is fantastic.

emacs or gvim

gvim: meh
emacs: ugh

I always wondered why it took so many decades for the *nix people to make a decent editor; by decent I mean "not limited to what a poor man's crappy terminal can do", using standard+customizable keys, supporting modern editor features, and just not being so half-assed as most Unix tools and applications (not the OS) are.

And now they have such editor - Kate. Why not using such a fine piece of software?

>>27
Because vim and emacs > kate.

>>28
Why? Or just because?

Because it's more efficient. Sure, you could reach for the mouse  and search the menus for that one function you're looking for. Sure, you can press the left arrow-key to the end of the line, and press Enter to add a new one. Or, you can do the same thing in gvim/emacs in seconds with a few keystrokes. (Of course you can search the menus as well, if that's how you enjoy working, both emacs and gvim has menus)

Anyways, vim/gvim > everything.
Why? because of the shortcuts and the general efficiency of it. Of course you need to spend a little time setting up the config file, but once you've done that, you'll never return to kate or any other editor.

vi is a wonderful editor when you just want to make a quick change to a system file. VIM, however, is a bloated sack of shit. Emacs is just crap, period.

once you need to do more than add a line to a file (say, if you need to cut and paste words or lines) then you want nano.

If what you want is an IDE, then Ajunta is the best choice for unix systems (with visual studio being the best one for windows).

VIM and Emacs are for pretentious gasbags.

You know what's great about Unix? You don't need an IDE because the system is an IDE.

Personally I think nano is good for making quick changes, but when I want to make more extensive changes I switch to vim because I can do it faster.

I've been meaning to try emacs so I can flame emacs users without having to lie when people ask if I actually know what I'm talking about.

>>30
Sure, you could reach for the mouse  and search the menus for that one function you're looking for

I rarely do that in UltraEdit. I have key bindings. ANY key bindings. Standard key bindings used in other programs, plus my own. I don't have to type ESC, d, $, a to delete all to the end of the line. I just type Ctrl+K. And so on. Frequent tasks get shorter, easier to remember keys. Similar tasks get similar keys. And since it's not Unix, I can freely use virtually all keys on my 102-key keyboard.

Oh, and before you mention it, yes, UltraEdit has customizable highlighting, bracket matching, regular expression search and replace, several clipboards, bookmarks, immediate search (like emacs), code folding, autocompletion, columns mode and column operation (including arithmetic), binary safe hexadecimal editor, large file disk-based editing, text formatting, macros, plain text config, Unicode and CRLF conversion, grep, external apps binding, shell, and many other features. All that while maintaining user-friendly, fast, standard, fully-functional keys, and being notably smaller and faster than Kate. You can also have menus and toolbars - fully customizable ones, although I don't use them.


you can press the left arrow-key to the end of the line, and press Enter to add a new one

LOL. You've been using old Unix for too long. There's an End key there. End+Enter is all you need. Still easier than exiting editing mode and all that crap.


>>32
You don't need an IDE because the system is an IDE

Cliche. You can't browse a class hierarchy with tail and grep, can you?

>>33
Age for truth. the whole point of an IDE is to have your tools together, in one place, functioning in an automatic manner.

I'm just learning programming, so I don't know what it's like to work with a large project (I'm sure it's different), but for small projects I really like Anjuta. Of course for a large project you're going to want something better than find . -name *c -exec grep foo \{}; (Or is it "-exec (grep foo) \{};"? another argument for autmation -- you don't have to keep track of a bunch of CLI arcana).

>>33

Still easier than exiting editing mode and all that crap.
End+Enter also works in editing mode, no need to exit.
Btw, do "set insertmode" to "use Vim as a modeless editor.".

Frequent tasks get shorter, easier to remember keys
like "imap <c-k> <esc>d$a" to delete all to the end of the line while in insert mode =o?

I can freely use virtually all keys on my 102-key keyboard.
me too.

the problem is that vim was developed with functionality in mind, not usability. you have to manually adjust it to your needs.

>>34

find . -name *c -exec grep foo \{};
your shell sucks :o

14:04  ~/mem/dev/testing  $ grep XXX **/*m
gnustep-examples-1.0.0/gui/Classes/NSProgressIndicator/Threads/MainThread.m:  [field setStringValue: @"Status: Running auxiliary thread ... XXX.XXX%"];

.. i think i missed the point *cough* sorry.

i have some really small-scale projects i'm working on and vim worked fine for these so far. if i need to see a list of active buffers and a file- or taglist, "winmanager" (http://vim.sourceforge.net/scripts/script.php?script_id=95) proved to be useful. oh yeah, the "quickfix" feature of vim is also neat: the errorlog of the compiler/unittest-thingy/interpreter is saved to a buffer which allows you to jump directly to the error with one keystroke and fix it.

the problem is that vim was developed with functionality in mind, not usability. you have to manually adjust it to your needs.

I don't want to get a Ph.D. in Unix Editors and spend a week getting them to be half decent before I can edit php.ini. Especially when I can just use Kate or UltraEdit, which are, by default, quite good, and have a linear learning curve - you can start using them right away, and learn all the advanced features like column operations as you use and need them.

The first time you want something, you'll take a look at the menus. If it's a rare feature you won't be using, it'll be more productive to do so. If you find it useful, you'll see which key is it associated with and memorize it - or define your own if it sucks or there isn't any.

>>34
BTW, that's more easily done with my Ptools. I should release them some day. If I undestood that command correctly, I can do that with: pl c$ | doforall grep -f !! foo

They are meant to extend your shell with all sorts of regex-based gadgets, including but not limiting to regex-based globbing, recursive globbing, reverse quotes for any shell that doesn't support them, stdin/stdout handling (you can build 2D pipes which join and fork into more pipes!), access to HTTP, FTP, etc. resources as files and send them to a pipe, integrating PHP functions, listing files, processing file lists, and more.

lol who said emacs didn't have a help system or menus.
Really most of you are just arguing anything more complex than just typing text and using the mouse to highlight text is all you need.

>>38

And you keep making the assumption that guy_who_doesn't_like_your_favorite_editor = luser who needs half of what Notepad does.

I'm not a luser, and I hate mice for editing. I don't waste my time with that when I can select with the keyboard in several ways, usually faster than you would do in VIM (with or without Visual Mode).

40GET