Bambi Hambi - 01 August 2005 02:38 PM

mcdermd - 01 August 2005 11:41 AM

Jebedee - 31 July 2005 10:03 AM

Who’s going to use CLI with a Mac?

Actually, I’m sure there’s a whole hell of a lot of us. I’m comfy in a unix environment.

“I” use CLI all the time on Tiger. Tera taught me and it’s no big deal.

My first exposure to a computer (Note to Jeff Mincey:  It was an 8-bit Commodore that let me write to my Aunt Martha just as quickly as any computer I’ve used since.) was CLI.  Then some folks came along and invented this thing called the “Graphics Environment Operating System” (GEOS).  I got a Commodore mouse.  I clicked on buttons and drop-down menus.  Way cool!  It had scaleable fonts and proportional spacing and all kinds of nifty things.  Eventually, some guy in Cupertino hired the GEOS developers to create a similar GUI for him.  Later, with my IBM clone, I got onto the Internet.  For the first year, that was UNIX CLI.  What’s this WWW stuff, anyway?  Later I found out.  CLI is quick and sometimes it’s easier.  Usually, I prefer the GUI.

... JJ

Note:  I’ll bet there are fewer regular CLI users than users who know what a right click is for.

Jeff Mincey - 01 August 2005 04:19 PM

By the way, there are X11 versions of emacs around but has anyone seen a GUI version of vi? I suppose this would be blasphemy to the vi apostles but I confess to being curious nonetheless.

Why, Jeff, emacs has a vi mode Also, there are Aqua versions of emacs around.

Anyway, I do pretty much on the command line playing/working/developing with the UNIX underpinnings of OS X (Darwin Ports, etc.). Even though I have usually been using vi on that level, I recently use SubEthaEdit quite frequently. It is a nice and stripped down Cocoa-based code editor (has great support for collaborative editing, which I need quite often these days) and can be invoked from the command line with a simple “see” (needs some time to launch though).

Utz - 04 August 2005 10:47 AM

Anyway, I do pretty much on the command line playing/working/developing with the UNIX underpinnings of OS X (Darwin Ports, etc.). Even though I have usually been using vi on that level, I recently use SubEthaEdit quite frequently. It is a nice and stripped down Cocoa-based code editor (has great support for collaborative editing, which I need quite often these days) and can be invoked from the command line with a simple “see” (needs some time to launch though).

Three cheers for SubEthaEdit. Clean, sleek, plenty of power that doesn’t get in the way.

Also, an extra round of applause for my favorite ‘quickie’ editor, TextWrangler. It’s the free baby brother to BBEdit. Also, you can invoke TextWrangler from the command line by typing ‘edit’ and file name. Sweet.

Did I mention it’s free?