Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Add open command for issue URLs

The command will read the TM_ISSUE_URL variable from the current environment so you should set this in your project’s .tm_properties file.

The value should use ‘%s’ for where the issue should be inserted. E.g. for TextMate/.tm_properties we set:

    TM_ISSUE_URL = 'https://github.com/textmate/textmate/issues/%s';
  • Loading branch information...
commit 570d25795d4c68d0ac809073a238c40dabe26ccc 1 parent 10fb149
Allan Odgaard authored August 15, 2012

Showing 1 changed file with 46 additions and 0 deletions. Show diff stats Hide diff stats

  1. 46  Commands/Open Issue Link.tmCommand
46  Commands/Open Issue Link.tmCommand
... ...
@@ -0,0 +1,46 @@

5 notes on commit 570d257

Rob McBroom

Wouldn't it be nicer to use #157 instead of issue://157? That would allow direct pasting to/from a comment on GitHub and it would all just work. Bonus points if you can add support for GitHub's syntax for links to issues in other repos. :-) i.e. user/Repository#123

Allan Odgaard
Owner

I think that would clash a lot with other uses of the hash-character followed by a number.

Syntax for referring to other repositories might be useful, but personally I don’t need it — when I do, I might add it :)

Rob McBroom

I think that would clash a lot with other uses of the hash-character followed by a number.

How so? We're just talking about the assigned scope, right? So as long as you don't take away or override an existing scope for those strings, all the existing stuff should continue to work, would it not?

Syntax for referring to other repositories might be useful, but personally I don’t need it — when I do, I might add it :)

We use it quite a bit for Quicksilver (with all the plug-in repos, etc.) Seems like you would to, considering all the bundle repos. :-) In any case, one nice thing about that syntax is that you wouldn't even need to define $TM_ISSUE_URL to make it work. Not that I'm suggesting using that syntax all the time. I'd much rather just type/read #XXX (or even issue://XXX) if that works in the current context.

Allan Odgaard
Owner

As for clash, I mean if you have some commented CSS with hex colors (e.g. #000) then that would be underlined as a clickable issue.

As for issue://XXX that does work (i.e. w/o the brackets).

Rob McBroom

I see your point. I think the small distraction with be worth it, but OK.

Please sign in to comment.
Something went wrong with that request. Please try again.