Bundles and GitHub

To make it possible to find TextMate bundles by automatic tools such as TextMate Gem and the new GetBundles bundle (currently in review) the naming convention proposed is to include .tmbundle in the name of your bundle project.

Presently most bundles at GitHub use -tmbundle but likely because a dot was previously not allowed in a project name.

14 Comments

  1. 12 Aug 2008 | # Meta | ateM » Blog Archive » Project #3 - Fluid CSS TextMate Bundle wrote…

    [...] 2008-08-12 update:I've renamed the repository on GitHub to be fluid-css.tmbundle to conform to the naming suggested by Allan on the TextMate Blog. [...]

  2. 13 Aug 2008 | # Dr Nic wrote…

    The other challenge with github's naming limitations vs typical bundle names is that you lose the capitalisation and any parentheses. So JavaScript (jQuery).tmbundle becomes something like javascript-jquery-tmbundle. Does the TextMate gem + GetBundles cope with this? Is the "true" bundle name stored internally within the info.plist at all or could it be?

  3. 13 Aug 2008 | # Thomas Aylott wrote…

    Yeah, I originally filed the Project Naming: Allow Periods "." ticket: http://logicalawesome.lighthouseapp.com/projects/8570/tickets/285

    Not that the ticket has been fixed and deployed we should all be using .tmbundle. I recently went in and renamed all my bundles from -tmbundle to .tmbundle

    I highly recommend that anyone that currently has any bundles on GitHub also do that. Renaming projects was recently added to Github. This is a one-time step and you'll never have to think about it again.

    @rdnic Yes, teh true bundle name is inside the info.plist in the bundle. It really doesn't matter what the filename of the bundle is, as long as it has the extension .tmbundle

  4. 13 Aug 2008 | # Dr Nic wrote…

    As github don't offer a proxying/redirect service after renaming I don't think I'll be renaming any bundles (http://skitch.com/drnic/ug4c/i-probably-won-t-be-renaming-tmbundles)

    Hopefully the TextMate gem + GetBundles use the info.plist name when cloning these repos locally as the folder name. That would be very cool.

  5. 13 Aug 2008 | # Automatyczna instalacja TextMate Bundles « bendowski.pl wrote…

    [...] jest utrzymywanych w serwisie GitHub – to właśnie autorów tych dodatków dotyczy wpis na blogu MacroMates zachęcający do ustandaryzowania nazw projektów mających coś wspólnego z [...]

  6. 14 Nov 2008 | # Flug wrote…

    I' gonna stick to Dr. Nic's method. Maybe it's just to early to think about it, but surely necessary to publish our complaints.

  7. 26 Feb 2009 | # Solutions Log → Installing GetBundles on a Fresh Copy of TextMate wrote…

    [...] TextMate Blog — Bundles and GitHub [...]

  8. 12 Jun 2009 | # Milan wrote…

    Does the blogging bundle in TextMate 1.5.8 work with WordPress 2.7 or 2.8?

    I haven't been able to get it to work for ages.

  9. 12 Jun 2009 | # Milan wrote…

    It's really annoying, actually, since the big yellow error box that pops up vanishes as soon as you do anything. I have been trying to use Grab to get a screenshot of it, but without luck so far.

  10. 13 Jun 2009 | # Allan Odgaard wrote…

    Milan: Works for me with 2.7.1.

    You can change the output of the comment (via bundle editor) from “Show as Tool Tip” to something like “Create New Document” to get the error output copyable.

  11. 13 Jun 2009 | # Milan wrote…

    Here is the error it always produces when I try to fetch posts.

  12. 13 Jun 2009 | # Allan Odgaard wrote…

    Milan: That indicates that your configured end-point returns a redirect, so you just need to update that to the actual (permanent) location of your blog end point.

    This could be something like including ‘www’ in the URL or similar.

  13. 13 Jun 2009 | # Milan wrote…

    Thanks a lot.

    Unlike most TextMate users, I am not a programmer. I just like how well it works for editing HTML.

  14. 19 Nov 2009 | # My TextMate setup | BenKreeger.com wrote…

    [...] and foremost, GetBundles, GetBundles, GetBundles. Make sure you've got Subversion (you're on a Mac? You probably already have it then) [...]

Comments closed, you can use the mailing list for discussion.