Slashdot Mirror


TextWrangler 2.0 Freely Available

Newly released TextWrangler 2.0 is now free (as in beer). TextWrangler is a stripped-down version of the popular BBEdit text editor. TextWrangler has switched identities since 1.0, from being a text editor with an indeterminant purpose to a subset of BBEdit, a BBEdit Lite on steroids. It handles syntax coloring, scripting tools (perl, python, shell), and some Xcode integration. It does not include some of BBEdit's more advanced features like source control, CodeWarrior integration, glossaries, and creating text factories (though it can run existing saved factories). BBEdit remains $200, and TextWrangler still qualifies for BBEdit's $130 cross-upgrade price. Previous purchasers of TextWrangler qualify for a store credit (they will be notified via e-mail).

9 of 83 comments (clear)

  1. Re:Mac only by WCityMike · · Score: 2, Insightful

    Not exactly a prominent omission for an Apple.Slashdot.Org posting ...

  2. They had to do it by Fahrenheit+450 · · Score: 4

    Not a big surprise, really. With the exception of HTML editing, the crop of newer editors for OS X (TextMate, SEE, Smultron, etc.) were making BBEdit look like that smelly old t-shirt stuck at the bottom of the drawer. You used to love that shirt, but now there are a whole lot of new shirts for you to wear, only without all of the rips and stains.

    Since BBEdit is underfeatured and way overpriced for general text editing, Bore Bones had to do something to keep their name recognition alive...

    --
    -30-
    1. Re:They had to do it by commodoresloat · · Score: 3
      I have that smelly old t-shirt... it says "BBEdit: Software that Doesn't Suck." They sent it to me for free back when I ordered BBEdit 3.0. I pretty faithfully upgraded until right before 8.0. Not because 8.0 didn't also look cool, but because for my purposes I'm perfectly happy with 7.1.4.

      BBEdit REALLY doesn't suck. For basic text editing of course there are fine programs that are free, but for HTML and for other tasks that require a lot of text processing (supersmart search and replace, browsing multiple files, etc.) it is a godsend on the Mac. And it is ALL Mac; so intuitive it makes you want to drool with pleasure. There may be newer OSX text tools out there but I've had no need or desire to poke around at them, not with trusty old BBEdit around.

  3. Re:Emacs by rsmith-mac · · Score: 2, Insightful

    I know this is going to sound odd, but emacs feels out of place on a Mac. The X Windows version is completely ignorable, since even with good X11 support, X11 is not what the Mac is about. Now the Carbon/Aqua versions are a somewhat different beast, but emacs still brings in things like shortcuts that were developed in the PC world and don't make any sense in the Mac world.

    On the flip side there's BBEdit/TextWragler, apps written by guys who have been doing Mac stuff for years(Apple users are unusually loyal to Mac developers; it's one of the last markets where Shareware still works), and their products have been built from the ground up for the Mac because of that. In that respect, it works very well for the environment by doing what users expect out of Mac shortcuts, though it's really one of those "you have to use it to understand it" sort of things, it's hard to describe things that you do instinctively without thought.

    Though this could have changed somewhat by now, I haven't used a Mac version of emacs in over a year...

  4. Re:Emacs by McDutchie · · Score: 3, Interesting
    Why not use emacs?
    [...]
    And it works the same under MS Windows or X Windows.

    You answered your own question there, at least as far as most Mac users are concerned. The emacs user interface is completely foreign to a Mac environment.

  5. Re:Uhh... by pudge · · Score: 2, Informative

    I cant open my .php files with Text Wrangler though.

    I can. I did. I don't think you even tried it.

    When I open a .php file in TextWrangler, it shows as HTML, which is reasonable as a default (the HTML mode recognizes PHP code, but also HTML In addition). Others may prefer plain PHP syntax coloring instead, and you may modify that in your preferences (under "Languages").

    last i checked, .php files were 'text', so this program should be able to open it at least without color coding it..????

    If you think it cannot, you're obviously mistaken.

  6. Re:Uhh... by pudge · · Score: 2, Informative
    Then your system -- not TW -- thinks they are not text files. There's two ways file types are stored in the system, the old way and the new way.

    The old way:
    [pudge@bourque pudge]$ touch foo.php
    [pudge@bourque pudge]$ GetFileInfo foo.php
    file: "foo.php"
    type: ""
    creator: ""
    attributes: avbstclinmed
    created: 01/11/2005 16:09:31
    modified: 01/11/2005 16:09:31
    So it looks like it has no file type, unless I look at it in the Finder or somesuch, where I see it has a BBEdit document icon, and a Get Info shows "Kind: HTML file" and "Open with: BBEdit".

    Try both, and see what they say. Chances are it is either an unknown type, or it is known as a different, non-text, type.

    Either way, you can modify it in Get Info by changing to "Open with: TextWrangler" and then click "Change All..." to make that change permanent for all files with the ".php" suffix. Or, in TextWrangler, you can modify the options right there to open any files, not just text files (see the "Enable:" popup list in the file dialog, select "All Files"; you can make this the default, too, I believe).
  7. Re:Uhh... by pudge · · Score: 2, Informative
    Yeah, apparently SEE is "broken," declaring it of type "****", instead of "TEXT".
    [pudge@bourque pudge]$ GetFileInfo foo.php
    file: "foo.php"
    type: "****"
    creator: "Hdra"
    attributes: avbstclinmed
    created: 01/11/2005 18:14:10
    modified: 01/11/2005 18:14:10
    As you can clearly see, your assertion that this is a text file was incorrect, as SEE is telling the OS that it is not.

    The simple answer, if you wish to continue using SEE as your default for that file type, is to set TextWrangler to open any file by default, instead of only text files, as noted previously.
  8. Re:Emacs by babbage · · Score: 2, Informative
    I know this is going to sound odd, but emacs feels out of place on a Mac.

    That does sound odd.

    Put your cursor in almost any editable text field in your Mac -- the address bar in Safari, any text widgets in a Safari web page, the composition window in Apple Mail, etc -- and try a few Emacs keystrokes.

    Huzzah! The Emacs keystrokes work! The beginning & end of a line are [ctrl]+[A] and [ctrl]+[E]; delete-right is [ctrl]+[D], delete-right is [ctrl]+[H]; etc.

    Basically any application written in Cocoa -- not the Finder, but most of Apple's other core applications, and a lot of the post-OS9 third party stuff as well -- will get Emacs keybindings by default. If you know Emacs, or learned Emacs keystrokes in another application that uses them (I learned them in Pine and the Bash shell, personally), then you can transfer that finger memory to huge chunks of OSX.

    So... yeah. Emacs out of place on a Mac? Probably not... :-)