After the latest updates, the blogging bundle, even with previous fixes won't fetch posts.
Is there a fix available?
Are you running into the dateTime ruby problem[1]?
http://macromates.com/blog/2006/blogging-from-textmate/
Brett
On Aug 7, 2007, at 11:35 PM, Steven W Riggins wrote:
After the latest updates, the blogging bundle, even with previous fixes won't fetch posts.
Is there a fix available?
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Hi. I found alt solution to dateTime Ruby problem... Backgroud: i've install latest ruby in /usr/local/bin so bundled version of ruby is available too. But i add the following to the ~/.profile
export PATH="/usr/local/bin:/usr/local/sbin:/usr/local/mysql/bin:$PATH
so now if i type ruby in Terminall.app i get a newer version.
OK. If i run TM using icon in the Dock or in Application folder i get blogging bundle error while post/fetch posts. BUT if i start TM using `mate` command via Terminal.app - i have no errors at all! So warkaround is - start TM using `mate` command from Terminal.app.
On 8/8/07, Brett Terpstra brett@circlesixdesign.com wrote:
Are you running into the dateTime ruby problem[1]?
http://macromates.com/blog/2006/blogging-from-textmate/
Brett
On Aug 7, 2007, at 11:35 PM, Steven W Riggins wrote:
After the latest updates, the blogging bundle, even with previous fixes won't fetch posts.
Is there a fix available?
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
The reason it works if you start it from the Terminal (I think) is that it then inherits $PATH from bash; if you start via the dock / Finder / Quicksilver then it inherits $PATH from Finder, which doesn't include /usr/local/bin.
If you want it to always work, you can edit your ~/.MacOSX/environment.plist -- see http://www.macromates.com/textmate/manual/shell_commands#search_path(scroll down to the paragraph that starts with "Important").
On 8/8/07, Alexey Blinov nilcolor@gmail.com wrote:
Hi. I found alt solution to dateTime Ruby problem... Backgroud: i've install latest ruby in /usr/local/bin so bundled version of ruby is available too. But i add the following to the ~/.profile
export PATH="/usr/local/bin:/usr/local/sbin:/usr/local/mysql/bin:$PATH
so now if i type ruby in Terminall.app i get a newer version.
OK. If i run TM using icon in the Dock or in Application folder i get blogging bundle error while post/fetch posts. BUT if i start TM using `mate` command via Terminal.app - i have no errors at all! So warkaround is - start TM using `mate` command from Terminal.app.
On 8/8/07, Brett Terpstra brett@circlesixdesign.com wrote:
Are you running into the dateTime ruby problem[1]?
http://macromates.com/blog/2006/blogging-from-textmate/
Brett
On Aug 7, 2007, at 11:35 PM, Steven W Riggins wrote:
After the latest updates, the blogging bundle, even with previous fixes won't fetch posts.
Is there a fix available?
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Thanks!
What happened was that port got uninstalled, and thus opt, and thus the new ruby, and thus dead again.
Sigh.
On Aug 8, 2007, at 12:25 PM, Dougal wrote:
The reason it works if you start it from the Terminal (I think) is that it then inherits $PATH from bash; if you start via the dock / Finder / Quicksilver then it inherits $PATH from Finder, which doesn't include /usr/local/bin.
If you want it to always work, you can edit your ~/.MacOSX/ environment.plist -- see http://www.macromates.com/textmate/manual/ shell_commands#search_path (scroll down to the paragraph that starts with "Important").
On 8/8/07, Alexey Blinov <nilcolor@gmail.com > wrote: Hi. I found alt solution to dateTime Ruby problem... Backgroud: i've install latest ruby in /usr/local/bin so bundled version of ruby is available too. But i add the following to the ~/.profile
export PATH="/usr/local/bin:/usr/local/sbin:/usr/local/mysql/bin:$PATH
so now if i type ruby in Terminall.app i get a newer version.
OK. If i run TM using icon in the Dock or in Application folder i get blogging bundle error while post/fetch posts. BUT if i start TM using `mate` command via Terminal.app - i have no errors at all! So warkaround is - start TM using `mate` command from Terminal.app.
On 8/8/07, Brett Terpstra brett@circlesixdesign.com wrote:
Are you running into the dateTime ruby problem[1]?
http://macromates.com/blog/2006/blogging-from-textmate/
Brett
On Aug 7, 2007, at 11:35 PM, Steven W Riggins wrote:
After the latest updates, the blogging bundle, even with previous fixes won't fetch posts.
Is there a fix available?
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you
don't)
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you
don't)
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
I know about ~/.MacOSX/environment.plist but if i make changes there i got errors with VisualHUB.app. It can't convert movies anymore. I'm sure becouse of lost path to ffmpg but i have no idea how to make them all happy. And start TM form terminal is not a big price for that.
On 8/8/07, Dougal dougal@gmail.com wrote:
The reason it works if you start it from the Terminal (I think) is that it then inherits $PATH from bash; if you start via the dock / Finder / Quicksilver then it inherits $PATH from Finder, which doesn't include /usr/local/bin.
If you want it to always work, you can edit your ~/.MacOSX/environment.plist -- see http://www.macromates.com/textmate/manual/shell_commands#search_path (scroll down to the paragraph that starts with "Important").
On 8/8/07, Alexey Blinov <nilcolor@gmail.com > wrote:
Hi. I found alt solution to dateTime Ruby problem... Backgroud: i've install latest ruby in /usr/local/bin so bundled version of ruby is available too. But i add the following to the ~/.profile
export
PATH="/usr/local/bin:/usr/local/sbin:/usr/local/mysql/bin:$PATH
so now if i type ruby in Terminall.app i get a newer version.
OK. If i run TM using icon in the Dock or in Application folder i get blogging bundle error while post/fetch posts. BUT if i start TM using `mate` command via Terminal.app - i have no errors at all! So warkaround is - start TM using `mate` command from Terminal.app.
On 8/8/07, Brett Terpstra brett@circlesixdesign.com wrote:
Are you running into the dateTime ruby problem[1]?
http://macromates.com/blog/2006/blogging-from-textmate/
Brett
On Aug 7, 2007, at 11:35 PM, Steven W Riggins wrote:
After the latest updates, the blogging bundle, even with previous fixes won't fetch posts.
Is there a fix available?
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Aug 13, 2007, at 2:42 AM, Alexey Blinov wrote:
I know about ~/.MacOSX/environment.plist but if i make changes there i got errors with VisualHUB.app. It can't convert movies anymore. I'm sure becouse of lost path to ffmpg but i have no idea how to make them all happy.
Be sure t have the path to ffmpg also included in the PATH you set in environment.plist -- it would be worth figuring out why VisualHUB errors.
And start TM form terminal is not a big price for that.
You can also set PATH in Preferences -> Advanced -> Shell Variables.
On 8/14/07, Allan Odgaard throw-away-1@macromates.com wrote:
On Aug 13, 2007, at 2:42 AM, Alexey Blinov wrote:
Be sure t have the path to ffmpg also included in the PATH you set in environment.plist -- it would be worth figuring out why VisualHUB errors.
Hm... i check VisualHUB logs and found that in uses full path to ffmpeg (/Library/Application Support/Techspansion/'vh124ffmpeg) so its something different. The error itself is sounds like "sh: line 1: date: command not found (127)". No logs nor something i can check to see exactly command VisualHUB is issued. So... For now i'll stick with starting TM from terminal (or maybe its time to upgrade build-in MacOS ruby ;)
You can also set PATH in Preferences -> Advanced -> Shell Variables.
Setting PATH=/usr/local/bin doesn't help. (this is where new ruby is) as well as setting it to /usr/local/bin:$PATH
-- Alexey Blinov
On Aug 15, 2007, at 5:52 AM, Alexey Blinov wrote:
You can also set PATH in Preferences -> Advanced -> Shell Variables.
Setting PATH=/usr/local/bin doesn't help. (this is where new ruby is) as well as setting it to /usr/local/bin:$PATH
You need to set the PATH to *all* the folders with your shell commands (and $PATH is not expanded) -- the manual has an example of all these paths.
This is also why your other program failed with the “date not found” error.
-
Alexey Blinov -
Allan Odgaard -
Brett Terpstra -
Dougal -
Steven W Riggins