That did the trick, thanks Brad!
On May 26, 2006, at 11:17 AM, Brad Choate wrote:
> When you specify *.tmbundle, svn only updates the existing
> bundles. Just do "svn up" and it will update everything in the
> Bundles directory, including new ones.
I want to try out the GTD Bundle but when I run the bundle's "Help"
command I get the following error:
/bin/bash: line 39: SmartyPants.pl: command not found
Any chance someone can help me decipher this?
Peace
Mike Gregoire
This morning the TextMate RSS feed announced a new GTD bundle, and I
did the usual bundle update:
cd /Library/Application\ Support/TextMate/Bundles
svn up *.tmbundle
The GTD bundle never got installed, however. I checked /Library/
Application Support/TextMate/Bundles/ and Bundles (disabled) but
it's not there.
Even ran "svn up..." again but still no go.
Do I need to do something special to get GTD?
TIA,
- Dave Winzler
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
With such a great markdown/multimarkdown bundle combination, and now
with CSS Preview, I am doing more and more writing/publishing with
prince from Textmate. However, I have to use a shell command to run
prince. I have tried to hack the screenplay bundles command without
much success. What I am trying to write is:
1. convert a multimarkdown (need multi's footnotes) file with
declared css file to html (or xml)
2. tell prince to run the file with the css file "prince -s /
file/css /tmp/$DST.HTML /tmp/" getting the css file name from the
header in the html file so I don't have to tell prince where it is.
3. open the generated /tmp/$DST.PDF il in preview.
I can get prince to run, but not glob the css file name. My end
product is a PDF of the html source file. Cutie, but not what I want.
Thanks in advance for any help, or if others would like to make this.
Robert
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFEZNn30ZwlS5OIzRcRAus2AJwP6+gcwhFwT4FDWUljZdGBHB4izACeMj1z
TETVHHDSqVtg9/BRaAxwUqE=
=8gsc
-----END PGP SIGNATURE-----
Hi all - new to the list, loving TextMate so far.
Quick question that I cannot seem to find the answer to. After having
customized all my snippets and such, what is the recommended backup
procedure, so that I don't someday lose all my customizations?
Will backing up the TextMate app suffice? Will I need to write a script
to exit the application before backup or is it possible to backup the
bundles and all in-place with the app running? [normally I do not backup
applications - just necessary prefs and such]
Just thought I'd ask.
--
Chris Chapman
DataSetGo
I'm just starting to use TM and coming from skEdit where I could set
the preview to which ever browser I wanted. Is there a way to do that
in TextMate?
Josh
From the release notes:
"If you wish to set the default bundle yourself, the defaults key is
OakDefaultBundleForNewBundleItems."
Could you please give an example how to do this exactly?
Thanks. Oliver
I had Support/bin/CommitWindow.app all along, but I had some
extraneous files that got into Support/bin/CommitWindow.app/Contents/
MacOS/
CommitWindow.2.r3349
CommitWindow.r3349
CommitWindow.r3363
CommitWindow
CommitWindow.r3342
CommitWindow.r3350
CommitWindow.r3373
I'm not sure how they got there. But I wiped out the Support
directory and checked it out of SVN anew. And the problem went away.
Thanks,
Shiran
> On May 24, 2006, at 6:47 PM, Mikael Hultgren wrote:
>
>>
>> On 24 maj 2006, at 17.16, Chris Thomas wrote:
>>
>>>> <pastedGraphic.png>
>>>> If I go ahead and press 'Commit', it fails with the message:
>>>>
>>>> Subcommand 'commit' doesn't accept option '--diff-cmd arg'
>>>
>>> Somehow, on your system, the command line argument "--diff-cmd"
>>> to the CommitWindow is being interpreted as a filename. I'm
>>> baffled as to how this could happen.
>>>
>>> A workaround would be to uncheck the --diff-cmd and 'svn' items
>>> in the list. Anyone else see this problem?
>>>
>>
>> Yeah, i had the same problem. It resolved itself when i checked
>> out the new version of the CommitWindow.app.
>
> *forehead smack*
>
> Yes, you need to check out not just the bundle, but also the latest
> CommitWindow.app from the Support directory. Sorry I didn't make
> this clear in the checkin comments.
>
> Chris
