<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Personal Revelations of the Magnificent Megan M. &#187; TextMate</title>
	<atom:link href="/tag/textmate/feed/" rel="self" type="application/rss+xml" />
	<link>http://worldmegan.net</link>
	<description>(worldmegan)</description>
	<lastBuildDate>Wed, 13 Jan 2010 17:30:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>TweetDeck URL Fix: How I Got TweetDeck URLs Back Into My Browser, Where They Belong!</title>
		<link>http://worldmegan.net/2009/10/tweetdeck-url-fix-how-i-got-tweetdeck-urls-back-into-my-browser-where-they-belong/</link>
		<comments>http://worldmegan.net/2009/10/tweetdeck-url-fix-how-i-got-tweetdeck-urls-back-into-my-browser-where-they-belong/#comments</comments>
		<pubDate>Sun, 11 Oct 2009 01:19:24 +0000</pubDate>
		<dc:creator>Megan M.</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Adobe AIR]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[fix]]></category>
		<category><![CDATA[Links]]></category>
		<category><![CDATA[TextMate]]></category>
		<category><![CDATA[TweetDeck]]></category>
		<category><![CDATA[URLs]]></category>

		<guid isPermaLink="false">http://worldmegan.net/?p=3062</guid>
		<description><![CDATA[	I had this problem forever, and I finally fixed it, so I&#8217;m going to tell you how I did it. If you haven&#8217;t ever had a problem with TweetDeck, you won&#8217;t find this very interesting. Feel free to skip along if that&#8217;s the case. ;} The next time some poor crusader searches Google for &#8220;TweetDeck [...]]]></description>
			<content:encoded><![CDATA[<p></p>	<p><p>I had this problem <em>forever</em>, and I finally fixed it, so I&#8217;m going to tell you how I did it. If you haven&#8217;t ever had a problem with <a href="http://tweetdeck.com/">TweetDeck</a>, you won&#8217;t find this very interesting. Feel free to skip along if that&#8217;s the case. ;} The next time some poor crusader searches Google for &#8220;TweetDeck URLs do not open in browser&#8221; or &#8220;<a href="http://www.adobe.com/products/air/">Adobe <span class="caps">AIR</span></a> URLs broken&#8221; or &#8220;Why is TweetDeck / Adobe <span class="caps">AIR</span> opening all URLs in <a href="http://macromates.com/">TextMate</a>?&#8221; or &#8220;OH <span class="caps">GOD WHY WON</span>&#8217;T <span class="caps">ANYONE HELP ME FIX TWEETDECK</span>!?&#8221; their sad and lonesome prayers will (hopefully, possibly) be answered.</p><h3>Here&#8217;s what was going on&#8230;</h3><p>Every time I clicked a <span class="caps">URL</span> in TweetDeck, it brought up an error message in TextMate. I tried everything I could think of&#8212;reinstalling TweetDeck, Adobe <span class="caps">AIR</span>, and both, wiping out the preferences, fiddling with browser settings, trying to find a utility that could tell my computer that <span class="caps">ALL</span> web addresses should point to Firefox. I had no idea what was going on, and therefore, nothing worked.</p><p>I even tried emailing the TweetDeck folks <em>and</em> the Adobe <span class="caps">AIR</span> folks, but nobody could help me. I was completely confused, and finally, pathetically, I gave up.</p><h3>And here&#8217;s what I did that fixed it&#8230;</h3><p>But this week, full of chutzpah from my uber-exciting hard drive failure and the consequent series of miracles that ended in my complete recovery of all files and a very successful backup restoration (yes, I&#8217;m posting from that computer now&#8212;and because Apple no longer makes 100gb drives, I got a 250gb space upgrade. <span class="caps">NICE</span>, right?), I decided to try a few more things. Bringing over the Application Support &#38; Preferences from a computer with a <em>functioning</em> TweetDeck didn&#8217;t work&#8230;</p><p>But here&#8217;s what did:</p><p>With the knowledge that I had it backed up in several different places, <strong>I deleted TextMate.</strong> Poof!</p><p>Then I clicked a <span class="caps">URL</span> in TweetDeck. Incredibly, it went to Safari (not my default browser). But it was a start!</p><p>Then I went into Safari&#8217;s preferences and made sure my default browser was, in fact, set to Firefox. Then I closed Safari, closed TweetDeck, reopened TweetDeck, and clicked another link.</p><p>It went to Firefox, new tab and everything. <span class="caps">SUCCESS</span>!</p><p>When I <strong>restored TextMate</strong> to its former happily-installed glory, <em>the URLs continued to go straight to Firefox</em>. And I was fixed!</p><p>That&#8217;s all I have to say. I have information, and I shall disseminate it. What&#8217;s the internet for, after all? ;}</p></p>
 ]]></content:encoded>
			<wfw:commentRss>http://worldmegan.net/2009/10/tweetdeck-url-fix-how-i-got-tweetdeck-urls-back-into-my-browser-where-they-belong/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
