I've update my Ant bundle to include macros in the symbol list, as we
use a few in our build process. If anybody is interested, a patch is
attached.
Adam
Has anyone tried the bundle repository recently? It seems to be down,
ping also times out. Not sure if this is specific to my network
environment.. Is there anyone who is seeing the same symptoms?
--
Sangwhan Moon
Hi,
The 'Cleanup Whitespace' command in the Python bundle is very useful but is
cleaning up some whitespace that causes errors when I check for compliance
with PEP8. In the following code:
class test(object):
pass
PEP requires that the second line has no spaces, whereas 'Cleanup
Whitespace' adds 4. Would it be easy to fix this to be compliant with PEP?
Thanks,
Tom
--
View this message in context: http://www.nabble.com/Python-bundle-and-%27Cleanup-Whitespace%27-tp24558866…
Sent from the textmate users mailing list archive at Nabble.com.
Hi all,
I was wondering if there's a neat shortcut in Textmate to jump to capital
letters in word directly. Say I wanted my caret to jump to "That" in
"VeryLongWordThatIWantToEdit" using something akin to Option+right arrow
Thanks,
Stephane
Makes perfect sense. Thanks you for the through explanation... "_if_
there is a bundle in the Pristine Copy folder" was the part of the
puzzle I was missing... Thanks again!
>>>> How do you guys do it?
>>>
>>> I keep the bundles I hack on completely in ~/.../TextMate/Bundles,
>>> and
>>> those I mainly just _use_ in ~/.../Pristine Copy/Bundles. That way,
>>> editing my own bundles in TextMate changes exactly the files I want
>>> to
>>> push out, while my changes to other bundles is kept outside of their
>>> source tree and won?t lead to merge conflicts.
>>>
>>> Going back to git, when you create a repository on GitHub it gets
>>> you
>>> to a page containing step by step instructions for getting your
>>> source
>>> tree or local repository into the new remote repository.
>>
>> I'm not asking help on how to create a git repo or using github etc.
>> That's fine... What I'm not clear about is how you manage the
>> workflow
>> so that you don't have to copy the bundles to a different place and
>> just make the bundles you're using within TextMate repos themselves.
>> Or if you shouldn't do that at all? How do you "keep the bundles I
>> hack on completely in ~/.../TextMate/Bundles"? Do you manually copy
>> from the pristin/ folder first? Because the ~/.../TextMate/Bundles
>> only contains the changes you've made to~/.../Pristine Copy/Bundles
>> right? So you can't just push that without including what in Pristine
>> too. Or am I over thinking this somehow?
>
> Ah, I see. Sorry I misunderstood you before :-)
>
> ~/.../TextMate/Bundles only contains the changes from ~/.../Pristine
> Copy/Bundles _if_ there is a bundle in the Pristine Copy folder.
> That?s the destination TextMate installs to when you double-click
> bundles in the Finder, but you can just as well place bundles directly
> in ~/.../TextMate/Bundles.
>
> To summarize:
> - Assuming you start with a ?clean slate?, i.e. there is no version of
> your bundle in either ?/Bundles or ?/Pristine Copy, and
> - assuming you have a complete current version of your bundle around
> somewhere _else_, you would
> - copy (recursively) the bundle into your ?/TextMate/Bundles folder,
> then
> - do any git/generic-scm/other setup hubbub you want.
> After making changes in the Bundle Editor, your bundle contents will
> be changed _in place_, and you can perform your favourite version of
> the commit/push dance.
>
> As for combining a bundle?s Pristine Copy and tmDeltas, I find the
> easiest way for that to be:
> Just drag the bundle out of the Bundle Editor and drop it onto your
> desktop; the dropped bundle will include all of the deltas you want.
>
> Hope that?s more helpful?
> Martin
So I was in IRC asking Allan about this earlier today, but he said it was
still working in Leopard and
I could look in the source for any Snow Leopard issues (I've been
developing off and on with SL).
Well, I'm back on my Leopard side and it's broken here too. I
reinstalled the InputManager and still a no-go. It beeps at me when I
try to use the command (but as in SL, the bundle IS loaded as I can
see the command is there.)
So is anyone else suffering from a break with the "Edit in TextMate"
InputManager? I'd figured I'd poll the group at large before I start mucking
around or write it off as a non-working hack at this point.
-- Jesse
>> I got a HTML + CSS bundles that a few people use and I've been asked
>> to put them on github... So I'm looking into how you do that.
>> Ideally,
>> I'd like to just edit my bundles in TextMate, and push the update to
>> github when I come up with new snippet improvement, command, bug fix,
>> etc... But that mean I need to combine both of those (using mCSS as
>> example) first right?:
>>
>> ~/Library/Application Support/TextMate/Pristine Copy/Bundles/
>> mCSS.tmbundle
>> ~/Library/Application Support/TextMate/Bundles/mCSS.tmbundle
>
> I can?t see how this is related to git; don?t you have to do that
> anyway when you make your bundle available anywhere?
It's not directly related to git. I was just giving a little bit of
context so that people can understand what I'm trying to do. Now I can
see how my email subject might not be optimum... sorry.
>
>> How do you guys do it?
>
> I keep the bundles I hack on completely in ~/.../TextMate/Bundles, and
> those I mainly just _use_ in ~/.../Pristine Copy/Bundles. That way,
> editing my own bundles in TextMate changes exactly the files I want to
> push out, while my changes to other bundles is kept outside of their
> source tree and won?t lead to merge conflicts.
>
> Going back to git, when you create a repository on GitHub it gets you
> to a page containing step by step instructions for getting your source
> tree or local repository into the new remote repository.
I'm not asking help on how to create a git repo or using github etc.
That's fine... What I'm not clear about is how you manage the workflow
so that you don't have to copy the bundles to a different place and
just make the bundles you're using within TextMate repos themselves.
Or if you shouldn't do that at all? How do you "keep the bundles I
hack on completely in ~/.../TextMate/Bundles"? Do you manually copy
from the pristin/ folder first? Because the ~/.../TextMate/Bundles
only contains the changes you've made to~/.../Pristine Copy/Bundles
right? So you can't just push that without including what in Pristine
too. Or am I over thinking this somehow?
Thanks again!
Sorry for the noob question but...
I've just started getting into Git yesterday... (finally...) and I
can't quite figure out the best workflow to keep bundles on github up
to date.
I got a HTML + CSS bundles that a few people use and I've been asked
to put them on github... So I'm looking into how you do that. Ideally,
I'd like to just edit my bundles in TextMate, and push the update to
github when I come up with new snippet improvement, command, bug fix,
etc... But that mean I need to combine both of those (using mCSS as
example) first right?:
~/Library/Application Support/TextMate/Pristine Copy/Bundles/
mCSS.tmbundle
~/Library/Application Support/TextMate/Bundles/mCSS.tmbundle
How do you guys do it?
I did google it, but whatever I try I get a million posts talking
about bundles on Github and not how they actually get there...
I'm pretty shaky on Git still, so I understand if you don't have time
to explain the specifics, what I'd like is a general idea of the
workflow... I can research the rest. Thanks for any pointer!
