Is there any mechanism which would allow textmate to dynamically read my gitignore, and populate it into a variable ready for us in tm_properties?
It would be pretty cool to be able to say...
excludeInBrowser = "{$excludeInBrowser,$git_ignore,.tm_properties}"
As far as I know, you cannot execute any code* in .tm_properties.
A quick mockup of the script that would turn a .gitignore into a blob, would look like this:
paste -d, -s .gitignore
In theory this could be integrated into some build script to update your .tm_properties, but then TextMate would need to be restarted* to pick up the changes.
I suggest this little gem instead:
If you hold option (⌥) when using the (new) remove button to prune folder search results then the glob will be extended to exclude the undesired path, so that future searches exclude it by default.
Graham P Heath
*: IIRC / Correct me if I’m wrong
On June 25, 2015 at 3:03:31 PM, Carpii UK (carpii.uk@gmail.com) wrote:
Is there any mechanism which would allow textmate to dynamically read my gitignore, and populate it into a variable ready for us in tm_properties?
It would be pretty cool to be able to say...
excludeInBrowser = "{$excludeInBrowser,$git_ignore,.tm_properties}"
_______________________________________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 25 Jun 2015, at 22:54, Graham P Heath wrote:
In theory this could be integrated into some build script to update your .tm_properties, but then TextMate would need to be restarted* to pick up the changes.
*: IIRC / Correct me if I’m wrong
TextMate does detect changes to .tm_properties files.
Although it wouldn’t reload the contents of a file browser if a change causes a filtering pattern to change, but the next time the file browser reloads, it should use the new pattern.
Interesting, I'll look into this, thanks
On 25 June 2015 at 21:54, Graham P Heath graham.p.heath@gmail.com wrote:
As far as I know, you cannot execute any code* in .tm_properties.
A quick mockup of the script that would turn a .gitignore into a blob, would look like this:
paste -d, -s .gitignore
In theory this could be integrated into some build script to update your .tm_properties, but then TextMate would need to be restarted* to pick up the changes.
I suggest this little gem instead:
- If you hold option (⌥) when using the (new) remove button to prune
folder search results then the glob will be extended to exclude the undesired path, so that future searches exclude it by default.
Graham P Heath
*: IIRC / Correct me if I’m wrong
On June 25, 2015 at 3:03:31 PM, Carpii UK (carpii.uk@gmail.com) wrote:
Is there any mechanism which would allow textmate to dynamically read my gitignore, and populate it into a variable ready for us in tm_properties?
It would be pretty cool to be able to say...
excludeInBrowser = "{$excludeInBrowser,$git_ignore,.tm_properties}"
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
-
Allan Odgaard -
Carpii UK -
Graham P Heath