Me, again.
OK, so the GHCi fix was due to Alan's patch of the haskell bundle, not to my trashing my local bundle repository.
I've been playing with the 3rd party bundle Plain Text Wiki, but it doesn't seem to play nice with the fact that I modify some of the standard bundles (LaTeX templates and commands primarily). I've installed it in the standard place now, but then it will get wiped out upon update, right?
So, I tried the Experimental Wiki bundle: easy to do, perform the one command available. Apparently it should open a wiki based in a subdirectory of the bundle. I get the following error message, looks like a typo in the file linkify.rb
(Errno::EPIPE) from /Applications/TextMate.app/Contents/SharedSupport/Bundles/Experimental Wiki.tmbundle/Support/bin/linkify.rb:39:in `<<' from /Applications/TextMate.app/Contents/SharedSupport/Bundles/Experimental Wiki.tmbundle/Support/bin/linkify.rb:39 from /Applications/TextMate.app/Contents/SharedSupport/Bundles/Experimental Wiki.tmbundle/Support/bin/linkify.rb:38:in `open' from /Applications/TextMate.app/Contents/SharedSupport/Bundles/Experimental Wiki.tmbundle/Support/bin/linkify.rb:38 sh: line 1: /Users/ds08/Library/Application Support/TextMate/Support/bin/Markdown.pl: No such file or directory /tmp/tm_wiki/intro.html
I went into linkify.rb and noticed that the path is based on a HOME directory, so I altered that path name to be based on TM_SUPPORT_PATH. Now it works. And its cool (a bit clunky but useful).
It would be good to have the patch committed to the repository.
Best wishes David
On 30. May 2007, at 04:41, David F. Snyder wrote:
I've been playing with the 3rd party bundle Plain Text Wiki, but it doesn't seem to play nice with the fact that I modify some of the standard bundles (LaTeX templates and commands primarily). I've installed it in the standard place now, but then it will get wiped out upon update, right?
Could you be more specific? How does it not play nice? And what is “the standard place”?
[...] I went into linkify.rb and noticed that the path is based on a HOME directory, so I altered that path name to be based on TM_SUPPORT_PATH. Now it works. And its cool (a bit clunky but useful).
It would be good to have the patch committed to the repository.
Sure, please attach it :)
On 5/30/07 2:18 AM, "Allan Odgaard" throw-away-1@macromates.com wrote:
On 30. May 2007, at 04:41, David F. Snyder wrote:
I've been playing with the 3rd party bundle Plain Text Wiki, but it doesn't seem to play nice with the fact that I modify some of the standard bundles (LaTeX templates and commands primarily). I've installed it in the standard place now, but then it will get wiped out upon update, right?
Could you be more specific? How does it not play nice? And what is ³the standard place²?
"the standard place" is TextMate.app/Contents/SharedSupport/Bundles. When I modify default bundles, a support directory is created in my user dir, per the manual. It seems at some point that the environment variable TM_SUPPORT_PATH was getting set to $HOME/Application Support/TextMate/ (though today I'm not able to get this behavior ... ?). To prevent problems I just copied the downloaded plaintextwiki.tmbundle into the Bundles subdirectory ("the standard place" to install it, rather than double clicking the tmbundle file. Now the bundle commands work.
Not that I know how to do this (yet), but one thing that would make the Experimental Wiki bundle more attractive: a key to navigate the links on the page (including the "menu").
[...]
It would be good to have the patch committed to the repository.
Sure, please attach it :)
Done.
Best wishes David ----
David F. Snyder Texas State University, Math
On 30. May 2007, at 17:09, David F. Snyder wrote:
Could you be more specific? How does it not play nice? And what is “the standard place”?
"the standard place" is TextMate.app/Contents/SharedSupport/Bundles.
That’s not “standard”, that’s for default bundles only.
See http://macromates.com/wiki/Troubleshooting/RevertToDefaultBundles for a walk-through of the various locations bundles can be stored.
When I modify default bundles, a support directory is created in my user dir, per the manual.
No, TextMate does not create any local support directory.
It seems at some point that the environment variable TM_SUPPORT_PATH was getting set to $HOME/Application Support/TextMate/ (though today I'm not able to get this behavior ... ?).
It would be $HOME/Application Support/TextMate/Support IFF (if and only if) a) you created that folder and b) it has a ‘version’ file with a version larger than of the default support dir.
[...] It would be good to have the patch committed to the repository.
Sure, please attach it :)
Done.
Ah, back when I did this bundle, JS executions did not get the TM_* variables, that’s why I had to hardcode the path (which granted, would not work for all users).
I’ve updated the script.
On 5/31/07 6:13 AM, "Allan Odgaard" throw-away-1@macromates.com wrote:
[...] That¹s not ³standard², that¹s for default bundles only.
See http://macromates.com/wiki/Troubleshooting/RevertToDefaultBundles for a walk-through of the various locations bundles can be stored.
Oops, /Library/Application Support/TextMate/Bundles is the standard place for adding bundles, true dat. You never know what your "children" are up to! :)
I noticed that if the Exp. Wiki bundle is added using the BundleInstaller bundle then the patch doesn't work (or it didn't for me) but installing the bundle per the manual (into /Library/... Instead of ~/Library/.../Pristine Copy/) worked fine.
What's up with that?
Best wishes David
On 31. May 2007, at 17:38, David F. Snyder wrote:
I noticed that if the Exp. Wiki bundle is added using the BundleInstaller bundle then the patch doesn't work (or it didn't for me) but installing the bundle per the manual (into /Library/... Instead of ~/Library/.../ Pristine Copy/) worked fine.
What's up with that?
The Get Bundle-bundle will only install bundles at a version corresponding to the version of your Support folder.
Many bundles rely on the Support folder, and we do occasionally introduce new stuff in there (or change existing stuff), so it is important that these things are in sync -- checking out the Support folder just for one bundle is not an option, as it might then break all the default bundles (so it’s really all or nothing with the Support folder).
-
Allan Odgaard -
David F. Snyder