Those who have been waiting with upgrading to TextMate 2.0 should do it before upgrading to Yosemite. While 1.x will function many of the older bundle items rely on outdated system components not available in Yosemite.
This also marks the transition from alpha to beta for 2.0. Don’t let the beta designation scare you, this simply signifies that there are still planned features left to add. However it is already leaps and bounds above what 1.x offers with many people already using it in their everyday workflow.
As you transition to 2.0 you will find many great new features and improved bundles made much easier to manage with an included bundle manager in preferences. We have several blog posts detailing some of the new features. If you have problems finding a feature you can ask questions on the mailing list or contact us via email or Twitter. While still a work in progress you can also consult the manual, this will be filled out further in the coming months.
2.0 is a free update to all except those who purchased through Mac Heist for which there will be a modest upgrade fee.
Upcoming changes to OS X have caused us to make some changes in TextMate that have been causing some users to see a env: ruby18: No such file or directory error when running bundle items. This is caused by improper setup of the PATH variable, but lets go over what this variable does and how to correct the issue.
OS X comes with many command line tools that TextMate takes advantage of such as ruby, python, git, etc. To find these programs there is the environment variable PATH which is a list of paths that is used to find the required tools.
Note that while you may already have set the PATH variable for your shell (e.g. bash) it is not inherited in TextMate, as TextMate does not parse your shell setup scripts. For commands that require tools outside the default path list, like the LaTeX typeset command, we normally provide a list of common locations that TextMate should also search, so you normally should not need to change the PATH in TextMate.
To add to the PATH variable inside TextMate open Preferences and go to the Variables section and add a new item with the name of PATH. It is important that the value set augment the existing value instead of replacing it. To do this you should prefix the value with $PATH:. Example values for common uses:
If you are using TextMate 2.0 then the following info does not apply to you.
Many of the bundle items in TextMate are written with ruby and were coded for version 1.8. With Mavericks Apple has updated the default version of ruby to 2.0. While we recommend everyone switch to 2.0 we realize that some people are hesitant to switch during a major project or similar.
If you wish to use TextMate 1.x on Mavericks you will need to tell TextMate to use ruby 1.8 for bundle items by putting the path to it first via the PATH variable.
Open Preferences from the TextMate menu and go to the Advanced section and select the Shell Variables tab. Click the + button to add a new variable named PATH with a value of:
Make sure when copying this that there is no whitespace before or after the string and that it is on a single line.
If you wish to use another version of ruby for user scripts then set TM_RUBY to the path to your custom installed ruby. This is what will be used for Ruby → Run (⌘R), Ruby → Validate Syntax (⌃⇧V), and similar actions where user code is executed or scanned.
We previously sent out an email instructing 1.x users to update the shebang, those instructions are still valid, but we have since realized that the above is a simpler fix.
For those that live on the cutting edge by watching the nightly builds of the 2.0 alpha you have been cutoff from automatic updates by an unfortunate bug introduced in a recent build (a9401). You can update by opening preferences (⌘,) and switching to the Software Update tab (⌘5). Here you will notice that the last check was a while ago and can manually check for an update by clicking “Check Now”. After updating to a9409 or newer it will again check automatically for updates.
If you are using the “Normal Releases” option in this tab this bug does not affect you.
Recently we have been getting reports of some issues with Transmit, QuickCursor and other applications that use Apple events to communicate with TextMate. Thanks to Brian Webster and Michael Tsai this has been tracked down to a bug in the appleeventsd process in 10.8.2, hopefully this will be fixed quickly by Apple.
A workaround for Transmit would be to mount the server as a hard drive and open the files from there as it would bypass the bug, this would also work in other file transfer programs that have this feature. You can get more information and alternative workarounds at the their respective posts linked above.
The way to specialize things in TextMate is via the venerable scope selector matched against the current scope.
TextMate 1 created the scope by parsing the document’s content using a language grammar. Though sometimes, more context information is needed than what can be provided by the document’s content, which is why TextMate 2 has extended the information stored in a scope.
I’ve always wanted to allow end-users to tinker with their environment, my ability to do this is what got me excited about programming in the first place, and it is why I created the bundles concept, but there are limits to how much a bundle can do, and with the still growing user base, I think the best move forward is to open source the program.
The choice of license is GPL 3. This is partly to avoid a closed source fork and partly because the hacker in me wants all software to be free (as in speech), so in a time where our platform vendor is taking steps to limit our freedom, this is my small attempt of countering such trend.
I am also a pragmatist and realize that parts of the TextMate code base is useful for other (non-free) applications, so I may later move to a less restrictive license, as is currently the case with the bundles. For now, please get in touch with us if there are subsets of the code base you wish to use for non-free software, and we might be able to work something out.
Anything related to the code base, including contributions, can be discussed at the textmate-dev list or #textmate on freenode.net. Pull requests can be sent via GitHub but if you plan to make larger changes, it might be good to discuss them first if you want to ensure that we are interested in accepting a pull request for such change or simply want advice on how to go about it.
As you start to upgrade your system to the latest cat from Cupertino we have created a page on the wiki as a place to keep track of any issues and notes about Mountain Lion and TextMate. We will be keeping this updated if any new issues are found.
As in many other areas, TextMate 2’s layout engine has received a bunch of improvements under the hood. It’s sometimes hard to show these changes, at least until new features taking advantage of the changes begin to bubble up to the surface. Let’s take a tour of some of those new features now, so I can show you just how dynamic what renders has become.
Since the earliest word processors Find and Replace has been a standard feature expected by users editing almost any content. You can score extra points with the programming crowd if you support Regular Expressions, the swiss army knife mini-language of Find and Replace operations. Of course, TextMate 1 had both.
TextMate 2 adds some subtle refinements to this already strong collection of features.
Today we are pushing out a new nightly build for the 2.0 alpha that changes the minimum OS requirement to start requiring Snow Leopard, this change was made after checking the current statistics for 2.0:
10.8 2.0% 10.7 86.7% 10.6 11.1% 10.5 0.2%
With such a small percentage on 10.5 it makes sense to drop its support. Moving forward we may decide that requiring Lion will be a reasonable tradeoff as it provides many underlying benefits we could take advantage of. The usage statistics will be monitored to determine the feasibility of this move.
Also to help answer many of the more commonly asked questions we’ve put together a FAQ about 2.0.
TextMate has always had completion and, as I’ve said before, it remains the best reason to wear out your ⎋ (esc) key. The idea is simple and I bet you are already familiar with it, but, just to recap, if I had this Ruby code:
def initialize(min_x, min_y, max_x, max_y)
@min_x = min_x
@min_y = min_y
@max_x = max_x
@max_y = max_y
I could later use completion to finish off this line:
fail "max_x must be > min_x" unless @m‸
If I push ⎋ where my caret currently is (shown with ‸ above), TextMate will complete the variable reference to @max_y. It starts with @max_y, because that’s the closest instance variable reference to my caret (from the bottom of initialize()), meaning it had a high chance to be what I was referring to. It’s not really what I wanted though, so another press of ⎋ cycles me to the second choice of @max_x. That is what I want, so I add > and another @m. Then I can complete until I get @min_x (four presses of ⎋ or just one press of ⇧⎋ to go backwards, since it’s the furthest reference from my caret).
TextMate 1 allowed you to use variable references in Snippets and even to supply defaults or simple replacements for them. TextMate 2 expands a lot on what you can do with variable references and where you can use them.
In this article we will discuss:
The syntax of TextMate 2’s Format Strings
Where you can use them
The kinds of tricks these tools can help you accomplish
TextMate is and will always be a modern GUI application. However, developers are often forced to walk in two worlds using both GUI and command-line tools. TextMate has always bridged the gap between these environments with its trusty command-line sidekick: mate.
In TextMate 2, mate has learned some new tricks. A new partner-in-crime has also been introduced: rmate.
One of the features user have continually requested for TextMate is the ability to insert multiple carets. Allan, TextMate’s developer, was always a little resistant to the idea because it seemed to require the use of a mouse and he’s not a mouse guy. Well, he caved. You can now use a mouse to throw down multiple carets and then edit away.