>>25
if i were an EXPERT CAMERA BUILDER, i probably would
Name:
Anonymous2007-07-07 13:43 ID:/3TplMkP
vim most of the time.
Sometimes quanta if I'm working on a large web project. Always Eclipse if I have to program in Java.
Name:
Anonymous2007-07-07 16:42 ID:42ha1vV3
Building a camera -> Writing an OS
Developing the film -> Writing a text editor
Name:
Anonymous2007-07-07 16:52 ID:7QSKvu1P
Building a darkroom -> Writing a text editor
fix'd
You use editors to get shit done (write code), just as you use darkrooms to get shit done (develop a photo).
Name:
Anonymous2007-07-07 21:45 ID:NFqNib4k
TextMate, vim
Name:
Anonymous2007-07-08 1:29 ID:oIlaPT1+
Emacs. Anything else
1) isn't easily extensible;
2) is clumsy and awkward even with basic Emacs keybindings (say, GTK-based editors don't even have a «capitalize-word» function);
3) is poorly documented;
4) lacks non-systemwide inputmethods (except for special editors to input Japanese);
5) sucks;
6) is heresy.
I use notepad2. Notepad2 keeps things basic. I don't like the way most editors handle various advanced features so I'm currently writing my own fully featured text editor.
Name:
Anonymous2007-07-08 3:48 ID:3T8WG/dg
vim. simple. elegant. probably horribly written, but there doesn't seem to be a substitute that I can enjoy.
>>33
vim is indeed a pretty acceptable editor, but its codebase is made of #ifdef and fail.
Name:
Anonymous2007-07-08 11:33 ID:UdAdqkZ1
Emacs or vi. I learned them about 15 years ago, and never needed to learn another editor while working on about 5 OSs and 4 programming languages. A little initial effort for a lifetime of laziness.