Hi Paul!

I don't understand what that has to do with a proxy. For this command no connection is used. In addition I don't use a proxy. The Blog is at the local machine. Could this be happen because I updated ruby to 1.8.4?

Helge

Am 06.10.2006 um 09:14 schrieb Paul McCann:

Hi Helge,

...

I get an error with the blogging bundle. When I type cat->tab, than I get the following:

/usr/lib/ruby/1.8/net/protocol.rb:83:in `initialize': getaddrinfo: No address associated with nodename (SocketError)

This came up a couple of months ago, and Allan and Marc Brogle added in proxy support to the blogging bundle in order to try and get around the problem. See the help file in the blogging bundle for details (environment variable section). If you're behind an *authenticating proxy*, like someone I know all-too-well, you seem to be out of luck for now.

Cheers, Paul

---

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 6. Oct 2006, at 09:58, Helge Hartmann wrote:

I just saw, that this command fetches the available categories. Is this a new behavior? I never got something to choice. It behaved like a simple snippet.

The cat⇥ “snippet” fetches available categories, yes, that’s fairly new.

So you get the error only for that command? or also Fetch Posts?

An error like “getaddrinfo: No address associated with nodename” sounds very much like the end point URL you have given is invalid.

On 6. Oct 2006, at 13:29, Helge Hartmann wrote:

No, the Fetch Posts command works well. If it is of interest: My wordpress blog is at localhost:8888

Likely it was the port. The Category command had its own code for connecting to the server, I have now made it use the same as the rest of the blogging bundle.

On 6. Oct 2006, at 16:55, Helge Hartmann wrote:

When I copy the code from the bundle blog, it works. But the Update all Bundle Command doesn't update the built-in bundles. Is there a way to also update the built-in bundles?

Only by doing it manually. I renamed the title of the GetBundle command to “Update Installed Bundles” to make this more clear.

If you manually checkout the Blogging bundle, remember to keep it updated, remove it again the next time there is an update to TextMate, or do the checkout over the default version (inside TextMate.app/Contents/SharedSupport/Bundles).

On 8. Oct 2006, at 23:34, Helge Hartmann wrote:

When the server is down, the command will still generate an error. I thought, whether it would be a better behavior to catch the exception and then let the command act like the old snippet.

I don’t know what the error looks like, but it seems to me that a command which fetches something from your blog, should present you with an error, if it could not connect to that blog, rather than gracefully degrade. I.e. if it cannot connect to the blog, something is wrong, and the user should be told.

Also I found the performance of the categories fetch quite long. I think mostly there is a manageable amount of categories and the user simply want to type it in. So what do you think to have the old snippet and a fetch categories in addition?

The performance would likely be proportional to the speed of your network connection. Since creating a “Category:” snippet is trivial, I think we should leave that to users who for some reason finds fetching their categories too slow and/or do not have enough categories to need to fetch the list.

On 9. Oct 2006, at 22:49, a!e muñoz wrote:

Idea: what if you cache the categories from each blog? Thus the snippet would be usefull even when no connection is available (which is the case when I'm preparing stuff for posting while traveling...)

If you do a patch for this, I’ll gladly apply it :)

Keep in mind that users may have different end points configured, so caching should be aware of that.