Comments on: QotD: Text Editor http://nslog.com/2004/08/30/qotd_text_editor The Weblog of Erik J. Barzeski Wed, 23 May 2012 23:05:21 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Jon H http://nslog.com/2004/08/30/qotd_text_editor#comment-11191 Jon H Wed, 01 Sep 2004 14:01:07 +0000 http://nslog.com/2004/08/30/qotd_text_editor/#comment-11191 I always liked the original Edit from NeXTSTEP. It wasn't as limited as TextEdit, because it was also used in the development environment. It had a "developer" mode, with Unix integration (you could create menu items to invoke Unix scripts on the selection, etc). It also was integrated with GDB, with a little GUI control panel, breakpoints, and highlighting of lines as you stepped through code. I always liked the original Edit from NeXTSTEP.

It wasn't as limited as TextEdit, because it was also used in the development environment. It had a "developer" mode, with Unix integration (you could create menu items to invoke Unix scripts on the selection, etc). It also was integrated with GDB, with a little GUI control panel, breakpoints, and highlighting of lines as you stepped through code.

]]> By: Jeff http://nslog.com/2004/08/30/qotd_text_editor#comment-11190 Jeff Tue, 31 Aug 2004 15:51:41 +0000 http://nslog.com/2004/08/30/qotd_text_editor/#comment-11190 What about <a href="http://www.jedit.org">jEdit</a>? It has syntax highlighting, and even a PHP parser to show syntax errors to webmonkeys who use it for that purpose. It's open source, and free. What about jEdit?

It has syntax highlighting, and even a PHP parser to show syntax errors

to webmonkeys who use it for that purpose. It's open source, and free.

]]> By: Patrick Quinn-Graham http://nslog.com/2004/08/30/qotd_text_editor#comment-11189 Patrick Quinn-Graham Tue, 31 Aug 2004 11:32:46 +0000 http://nslog.com/2004/08/30/qotd_text_editor/#comment-11189 SubEthaEdit, pico/nano, and if none of the above are available emacs. (Er, on that <a href="http://www.microsoft.com/windows">that platform no one talks about</a> I use MetaPad, because it's faily not bad.) SubEthaEdit, pico/nano, and if none of the above are available emacs.

(Er, on that that platform no one talks about I use MetaPad, because it's faily not bad.)

]]> By: Macduck http://nslog.com/2004/08/30/qotd_text_editor#comment-11188 Macduck Tue, 31 Aug 2004 09:27:02 +0000 http://nslog.com/2004/08/30/qotd_text_editor/#comment-11188 Erik, you can build GUI version of the emacs :) check this out http://members.shaw.ca/akochoi-emacs/ Erik, you can build GUI version of the emacs :)

check this out http://members.shaw.ca/akochoi-emacs/

]]> By: Philip http://nslog.com/2004/08/30/qotd_text_editor#comment-11187 Philip Tue, 31 Aug 2004 07:57:00 +0000 http://nslog.com/2004/08/30/qotd_text_editor/#comment-11187 Call me a newbie (and I'll hit you), but I like to stick with the basics - I either use TextEdit (when doing stuff around X) or pico (for the console stuff). I am proficient in vi, but my navigation skills aren't quite enough for me to be using it on a regular basis without a cheat sheet. Call me a newbie (and I'll hit you), but I like to stick with the basics - I either use TextEdit (when doing stuff around X) or pico (for the console stuff). I am proficient in vi, but my navigation skills aren't quite enough for me to be using it on a regular basis without a cheat sheet.

]]> By: SoNSo1 http://nslog.com/2004/08/30/qotd_text_editor#comment-11186 SoNSo1 Tue, 31 Aug 2004 05:30:35 +0000 http://nslog.com/2004/08/30/qotd_text_editor/#comment-11186 BBEdit most definitely is my fav, even though I currently am using VisualSlickEdit on a PC at work. BBEdit was the first text editor I truly appreciated. I have since worked on a variety of platforms. I have gotten used to emacs. Vi gets a thumbs up for the incredibly unintuitive interface. SlickEdit is rather cool on the PC side. But since I loved BBEdit first, all subsequent text editors I have used are measured against it. BBEdit most definitely is my fav, even though I currently am using VisualSlickEdit on a PC at work. BBEdit was the first text editor I truly appreciated. I have since worked on a variety of platforms. I have gotten used to emacs. Vi gets a thumbs up for the incredibly unintuitive interface. SlickEdit is rather cool on the PC side. But since I loved BBEdit first, all subsequent text editors I have used are measured against it.

]]> By: Grayson http://nslog.com/2004/08/30/qotd_text_editor#comment-11185 Grayson Tue, 31 Aug 2004 01:31:46 +0000 http://nslog.com/2004/08/30/qotd_text_editor/#comment-11185 TextWrangler is my primary text editor. I have some applescripts that connect it with most of the other apps I use and to bring back some functionality that BBEdit has and I want. I use XCode for any code considerations, although I'm equally likely to have XCode and TW windows next to each other. Just depends on my mood, how much editing I'm doing, and what features I want. In the command line, pico. I dunno why, but I started using it and just keep doing so. I rarely edit in the command line since I'm always trying to cut and paste using the mouse, so just about anything with minimal functionality works well for me. TextWrangler is my primary text editor. I have some applescripts that connect it with most of the other apps I use and to bring back some functionality that BBEdit has and I want.

I use XCode for any code considerations, although I'm equally likely to have XCode and TW windows next to each other. Just depends on my mood, how much editing I'm doing, and what features I want.

In the command line, pico. I dunno why, but I started using it and just keep doing so. I rarely edit in the command line since I'm always trying to cut and paste using the mouse, so just about anything with minimal functionality works well for me.

]]> By: Jeff Harrell http://nslog.com/2004/08/30/qotd_text_editor#comment-11184 Jeff Harrell Mon, 30 Aug 2004 23:40:10 +0000 http://nslog.com/2004/08/30/qotd_text_editor/#comment-11184 Definitely SubEthaEdit. And everybody who does UNIX-type stuff should be passingly familiar with vi, because you just never know when you're going to be sitting in front of a VT100 wired up to a Power Challenge. Definitely SubEthaEdit. And everybody who does UNIX-type stuff should be passingly familiar with vi, because you just never know when you're going to be sitting in front of a VT100 wired up to a Power Challenge.

]]> By: Michael Williams http://nslog.com/2004/08/30/qotd_text_editor#comment-11183 Michael Williams Mon, 30 Aug 2004 22:25:02 +0000 http://nslog.com/2004/08/30/qotd_text_editor/#comment-11183 I use Vi[m]. As I suspect is the case for all of us, this is because it was the first "real" text editor I ever used. Real text editors are just too complex for people to invest the time and muscle memory required to develop individual preferences based on anything other than mild prejudice. Cases in point: I know of no one who has used more than the basic edit/save features of both emacs and Vim. I know of no one who has made the switch from vi or emacs to BBEdit. My own prejudice against BBEdit is the same as my own prejudice against emacs: from the outside they seem like horribly crufty, complex applications (in different ways). Doubtless both of these are unfounded. Uniquely and fatally for me though, BBEdit is not cross-platform and it's not Free. The first is an inconvenience if you move platforms a lot. The second is a show-stopper. It's not the money — I certainly don't mind paying for something as valuable as a good editor — but the remote prospect of BBEdit disappearing through factors outside my control. This doesn't bother me with something as ephemeral as, say, iTunes, but my editor is another matter! I use Vi[m]. As I suspect is the case for all of us, this is because it was the first "real" text editor I ever used. Real text editors are just too complex for people to invest the time and muscle memory required to develop individual preferences based on anything other than mild prejudice.

Cases in point: I know of no one who has used more than the basic edit/save features of both emacs and Vim. I know of no one who has made the switch from vi or emacs to BBEdit.

My own prejudice against BBEdit is the same as my own prejudice against emacs: from the outside they seem like horribly crufty, complex applications (in different ways). Doubtless both of these are unfounded.

Uniquely and fatally for me though, BBEdit is not cross-platform and it's not Free. The first is an inconvenience if you move platforms a lot. The second is a show-stopper. It's not the money — I certainly don't mind paying for something as valuable as a good editor — but the remote prospect of BBEdit disappearing through factors outside my control. This doesn't bother me with something as ephemeral as, say, iTunes, but my editor is another matter!

]]> By: Scott Stevenson http://nslog.com/2004/08/30/qotd_text_editor#comment-11182 Scott Stevenson Mon, 30 Aug 2004 22:06:55 +0000 http://nslog.com/2004/08/30/qotd_text_editor/#comment-11182 I primarily use Xcode and BBEdit, and occassionally use SubEthaEdit or vi if the situation calls for it. I primarily use Xcode and BBEdit, and occassionally use SubEthaEdit or vi if the situation calls for it.

]]>