Interview with SubEthaEdit Developer
WaxPoetic writes "There is a fun interview with the developers of SubEthaEdit, the only collaborative editor for Mac OS X. Topics covered include Apple slowing developing, BEEP, why they kept a free version, being a German Mac user, hopes for the Tiger release, and their hatred of metal interfaces."
While I don't use the networking capabilities of SubethaEdit, it has largely replaced BBEdit for me as my "editor of choice" for programming. Sleek, lightweight, and efficient (not to mention free for noncommercial use), it has a lot going for it.
I did have to write a python script that would work like bbedit's command line tool (with a few of the same options, such as -c), but once that was taken care of I started using it as my primary text editor.
Integrate Keynote and LaTeX
I recently switched to Mac OS X and gave bbedit a try (I also tried the top rated editors from Macupdate).
I ended up forcing myself to finally learn to use emacs. It has been worth it.
http://www.inf.unibz.it/~franconi/mac-emacs/
Thought I mention it even though SubEthaEdit is pretty handy too.
This paid my last vacation, it mi
I'd like to add my voice to the praise for SEE we've already seen. I've only tinkered with the collaborative editing on my home network (and it's very impressive), but without that feature SEE would still be my editor of choice, and I've been through the expansive .emacs and minimal vi mastery stages.
Just this morning I noticed that when editing a CSS file, SEE will not only give you a drop-down box of all your symbols / definitions, but also place an icon next to them identifying them as ID definitions, class definitions, and so on.
It's small, clean and extremely funcional - it feels pristine to use. I'd absolutely recommend trying it out, whether the collaborative features interest you or not.
I think Apple Germany should invest more in marketing [...] placing a few TV ads would be a good start.
Hehe.