This repository is an external command for Homebrew. It helps you manage bundles for the popular TextMate editor, like Homebrew does for apps.

Or, in other words: it’s a Homebrew tap that allows you to use the command line to search, install, and uninstall TextMate bundles.

Consider this tap untested. Do not use it unless you have backed up your important data.

Issues and pull requests are welcome.

This tap is different to most other taps because it contains executable code.

Even if you are very familiar with Homebrew taps, and even if you use them regularly without problems, you may want to be careful with the external command introduced by this tap.

Be warned that this tap installs and deletes things willy-nilly inside your ~/Library/Application Support/TextMate/Pristine Copy/Bundles folder; you may want to take extra care to back up this particular folder before you even tap this repo.

This tap provides a brew tm command, which has the following features, all via the command line:

• Install one or more TextMate bundles

• Uninstall TextMate bundles, or reinstall them

• Search for TextMate bundles inside the repository

• Shorthand for opening a TextMate bundle’s homepage

• Support for editing and auditing package files (Casks) for TextMate bundles

1. Make sure you have Homebrew installed.

2. Update TextMate to the latest version. You can do this either manually or via brew cask reinstall textmate.

3. Run brew tap claui/textmate to tap into this repository.

Run brew tm for information on how to use this tap.

Search for TextMate bundles that support 6502 assembly:

$ brew tm search 6502
==> Partial Match
tm-6502-assembler

Install the tm-6502-assembler bundle directly into TextMate:

$ brew tm install 6502-assembler

If you experience any issue using brew tm, do not submit an issue to the Homebrew project.

Instead, try the following steps in any order:

• Run brew update-reset && brew update to make sure your Homebrew installation is up to date. (Note that this will reset any changes you have made to taps.)

• Run brew untap claui/textmate and see if the problem goes away. Re-tap by running brew tap claui/textmate.

• Run brew tm to list all bundles you have installed, then brew tm uninstall --force one bundle at a time.

• Go to /usr/local/Caskroom and delete all the directories that start with tm-.

• Search the homebrew-textmate repo on GitHub for the same or similar issues.

• Follow Homebrew’s troubleshooting steps.

• If you are trying to contribute to the repo, the easiest way is to just work in the tap directly. Go to /usr/local/Homebrew/Library/Taps/claui/homebrew-textmate and work from there.

• If none of these steps help, file a new issue with the homebrew-textmate project. Do not submit an issue to the Homebrew project if the issue seems to be related to TextMate bundles, or to the brew tm command.

Feel free to fork, and contribute to, this repository in any way you like, for example in one or more of the following ways:

• create new Casks for (official or unofficial) TextMate bundles,

• submit pull requests to have your work merged with this repo,

• report issues, or

• contribute features or bug fixes.

Contributing Casks for TextMate bundles is easy. They are largely compatible with the Cask Language Reference; the only actual technical difference is that it introduces a new tmbundle stanza.

An easy method to create a new Cask for TextMate bundles would be to look at the examples and learn/copy/paste from them.

You can also find excellent documentation for the Cask Language if that’s more your thing.

The Caskroom repo also has a detailed tutorial on creating new Casks.

The main difference between regular Casks and brew tm-style Casks is that the latter introduces a new tmbundle stanza. The tmbundle stanza is needed to install TextMate bundles to the appropriate directory. The stanza can be used like any other artifact stanza in the Cask definition language.

When following the Caskroom’s instructions, be sure to apply the following modifications:

• When you choose or generate a token for your Cask, always prepend it with the tm- prefix when it’s a TextMate bundle.

• To edit a Cask for a TextMate bundle, use brew tm audit instead of brew cask audit.

• To test a Cask for a TextMate bundle, use brew tm install instead of brew cask install.

• To audit a Cask for a TextMate bundle prior to submitting a PR, use brew tm audit instead of brew cask audit.

• Use the claui/homebrew-textmate repository instead of caskroom/homebrew-cask.

• When writing a Cask for a Textmate bundle, use the tmbundle stanza instead of app.

• The section Finding a Home For Your Cask does not apply for TextMate bundles. You can safely ignore it.

• When you’re ready to submit your pull request, the base fork should be claui/homebrew-textmate @ master, and the head fork should be my-github-username/homebrew-textmate @ my-new-cask.

The command line is good for automating things, for example for unattended mass deployment. Also, some people just generally prefer command-line workflows over a GUI.

Chances are you don’t; in that case, the brew tm command and the homebrew-textmate repository are probably not for you.

No.

No.

No.

Nothing wrong in the least; TextMate’s list of built-in bundles is perfectly fine.

The brew tm command and this repo simply want to be an alternative method, designed for people who prefer a CLI workflow, or need to automate installing/uninstalling TextMate bundles for one reason or the other.

While the brew tm command does not support the Preferences » Bundles list built into TextMate today, it may do so in the future. In the meantime, you can freely use one or the other interchangeably, or both at the same time. They should play well with each other.

No. Managed bundles should work alongside the brew tm command without any issues. You can use one or the other, or both.

No.

The brew tm command should be pretty self-explanatory; being familiar with Homebrew won’t hurt though.

No.

You don’t need to be familiar with the brew cask command, although it will not hurt. In essence, the brew tm command is not much more than a façade to brew cask but with a focus on TextMate bundles.

In Homebrew, you can add custom features only if you bring along your own unofficial subcommand.

I don’t believe the Homebrew project will ever be an appropriate home for TextMate bundles. Homebrew has a strong focus on features which are useful for many users (and rightly so).

In my personal opinion and judgement, the TextMate ecosystem is not notable enough.

The good thing is that Homebrew allows – and, in fact, encourages – users to extend Homebrew by tapping into repos to their hearts’ content.

Homebrew offers a brew cask command which allows you to manage packages related to GUI apps on macOS.

Homebrew also offers external commands to extend the features of Homebrew.

This tap takes the brew cask feature and applies it to TextMate bundles.

For installing and removing TextMate bundles, brew tm uses a few (unsupported) implementation details of TextMate.

It is part of a shared philosophy of many package managers that installing software should be free from needless user interactions.

The brew tm command uses an implementation detail of TextMate to circumvent the confirmation dialog while installing a TextMate bundle.

Probably not, but minor cosmetic issues are possible.

There are a few possible points of contact where the brew tm command will cause Homebrew itself to produce errors.

One of them is that Homebrew keeps a bit of metadata inside the /usr/local/Caskroom/ hierarchy. This metadata will include instances of the tmbundle artifact stanza, which is proprietary for TextMate-related Casks.

The tmbundle stanza is unknown both to Homebrew and to the brew cask command. Homebrew does not expect metadata to contain tmbundle entries, which possibly leads to warnings or error messages. If you experience issues, refer to the Troubleshooting section.

I’m not aware of any major issues. However, brew tm relies heavily on implementation details in TextMate. Such details can change at any moment on TextMate’s end without notice. This can break brew tm, and it won’t be TextMate’s responsibility. (Any project is free to change its private implementation details at its own discretion.)

I strongly recommend that you prepare for this by making frequent backups. At the very least, those backups should include your ~/Library/Application Support/TextMate folder and all of its subfolders.

Yes.

brew tm will not be aware of files you have installed manually; it won’t assist you with uninstalling if you later choose so.

Apart from that, everything should be fine.

Yes.

If you’re referring to a bundle shown in TextMate » Preferences » Bundles, you can uninstall it by removing the check mark in the list.

If you’re referring to a bundle you have installed manually, you will find it in the ~/Library/Application Support/TextMate/Pristine Copy/Bundles directory. Simply delete that bundle to uninstall.

Note that either way, your manual modifications will be kept even after the bundle has been deleted. This is expected behavior.

The brew tm command does not support this feature yet.

It uses the ~/Library/Application Support/TextMate/Pristine Copy/Bundles directory as its (hard-coded) default location for the time being.

Making manual changes to bundles is unrelated to brew tm, and should continue to work as expected.

TextMate goes to extra lengths to preserve each and every manual change you have made, no matter which method you have used to install or uninstall the bundle. Your choice of installation method does not affect the way TextMate preserves your manual changes.

The brew tm command cannot help you with that yet. A future release might offer a feature to allow you to undo your custom modifications.

Run brew untap claui/textmate.

Not yet. This would involve splitting the repository in two or more taps. I don’t think this would be worth the additional effort on the user’s side, at least for now.

Maintaining a local clone, e. g. under your home directory, is probably not worth the hassle that comes with it. As all the brew subcommands only look at the taps under /usr/local/…, and ignore everything else, you’d have to take care of syncing your custom repo with the tap all the time. It’s definitely possible; however for testing, my personal opinion is that it this brings pain, sorrow, and confusion.

Instead, make sure you have done brew tap claui/textmate once; then I recommend that you go to /usr/local/Homebrew/Library/Taps/claui/homebrew-textmate and simply work from there.

This tap, including the brew tm command and all Cask definitions for TextMate bundles, is in no way affiliated with, nor is it endorsed by, the TextMate project nor any of the people who maintain that project, nor MacroMates Ltd., nor the Homebrew project nor any of its maintainers, nor the Caskroom organization.

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

The idea for this repo comes from a discussion thread started by じょいすじょん on the TextMate mailing list.