<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Kids in the Park</title>
	<atom:link href="http://www.red-sweater.com/blog/68/kids-in-the-park/feed" rel="self" type="application/rss+xml" />
	<link>http://www.red-sweater.com/blog/68/kids-in-the-park</link>
	<description>Mac &#38; Technology Writings by Daniel Jalkut</description>
	<lastBuildDate>Wed, 18 Jan 2012 18:10:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Red Sweater Blog &#187; Blog Archive &#187; WordPress 2.0</title>
		<link>http://www.red-sweater.com/blog/68/kids-in-the-park/comment-page-1#comment-630</link>
		<dc:creator>Red Sweater Blog &#187; Blog Archive &#187; WordPress 2.0</dc:creator>
		<pubDate>Tue, 24 Jan 2006 21:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/?p=68#comment-630</guid>
		<description>[...] http://www.red-sweater.com/blog/68/kids-in-the-park [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.red-sweater.com/blog/68/kids-in-the-park" rel="nofollow">http://www.red-sweater.com/blog/68/kids-in-the-park</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Red Sweater Blog &#187; Blog Archive &#187; WordPress 2.0</title>
		<link>http://www.red-sweater.com/blog/68/kids-in-the-park/comment-page-1#comment-627</link>
		<dc:creator>Red Sweater Blog &#187; Blog Archive &#187; WordPress 2.0</dc:creator>
		<pubDate>Tue, 24 Jan 2006 20:50:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/?p=68#comment-627</guid>
		<description>[...] On the subject of feeds, Eric Albert of Out of Cheese recently asked me if there was a method of subscribing to all of the comments made to the blog. He observed that my increasingly sophisticated readership manages to inject some pretty interesting information &#8220;below the fold&#8221; on some of my entries. While each entry offers a link for subscribing to that particular entry&#8217;s comments, I had never noticed a method for subscribing to the whole kit and caboodle. But I noticed on WordPress&#8217;s administrative interface, that it showed me a running tally of just such a thing. A little research discovered a variation on the RSS URL that does just that. I was pleased to see that it continues to work as expected in WordPress 2.0. I realized during this examination that I didn&#8217;t previously list the basic &#8220;subscribe&#8221; link anywhere on the page. For those unlucky enough to be running a browser that doesn&#8217;t put a big obvious &#8220;RSS&#8221; button in your address bar, that might come in handy. So I&#8217;m adding two links to the main sidebar: one for the blog, and one for the comments. I&#8217;ve said it before: my readers make this place worth coming back to. I love the interplay between &#8220;really smart people&#8221; that takes place after I&#8217;ve left the building. Hopefully by subscribing to the comments feed, you&#8217;ll be able that much more likely to notice when you have something valuable to contribute. [...]</description>
		<content:encoded><![CDATA[<p>[...] On the subject of feeds, Eric Albert of Out of Cheese recently asked me if there was a method of subscribing to all of the comments made to the blog. He observed that my increasingly sophisticated readership manages to inject some pretty interesting information &#8220;below the fold&#8221; on some of my entries. While each entry offers a link for subscribing to that particular entry&#8217;s comments, I had never noticed a method for subscribing to the whole kit and caboodle. But I noticed on WordPress&#8217;s administrative interface, that it showed me a running tally of just such a thing. A little research discovered a variation on the RSS URL that does just that. I was pleased to see that it continues to work as expected in WordPress 2.0. I realized during this examination that I didn&#8217;t previously list the basic &#8220;subscribe&#8221; link anywhere on the page. For those unlucky enough to be running a browser that doesn&#8217;t put a big obvious &#8220;RSS&#8221; button in your address bar, that might come in handy. So I&#8217;m adding two links to the main sidebar: one for the blog, and one for the comments. I&#8217;ve said it before: my readers make this place worth coming back to. I love the interplay between &#8220;really smart people&#8221; that takes place after I&#8217;ve left the building. Hopefully by subscribing to the comments feed, you&#8217;ll be able that much more likely to notice when you have something valuable to contribute. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Jalkut</title>
		<link>http://www.red-sweater.com/blog/68/kids-in-the-park/comment-page-1#comment-403</link>
		<dc:creator>Daniel Jalkut</dc:creator>
		<pubDate>Sun, 25 Dec 2005 16:26:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/?p=68#comment-403</guid>
		<description>Hi CJ - thanks for bringing to light a few important issues:

1. I often assume an expert level of experience with AppleScript among the recipients of my scripts.
2. The script as modified to support iTerm makes it so you *have* to have iTerm. That&#039;s no good!

I will fix the iTerm problem ASAP. In the mean time, one thing you can do is just pick *any* application on your computer when it asks for iTerm.  In fact, probably just pick Terminal.  It will then mess up the script for iTerm, but should leave it working fine for Terminal.

The question as to where scripts should be installed is somewhat complicated, because different &quot;script runners&quot; look for scripts in different places. However, the most standardized location is that used by Apple&#039;s Script Menu. This location is under the &quot;Library&quot; folder in a folder called &quot;Scripts&quot;. For instance:

~/Library/Scripts/

If you install my FastScripts utility you can use it to locate and/or create global and application-specific script folders using this convention. The scripts will be accesible from Apple&#039;s script menu, FastScripts, and a number of other applications out there.

Note that to make this script really useful, you&#039;ll want to hook it up to a keyboard shortcut. FastScripts is also an excellent choice for accomplishing this.

Thanks for the comments,
Daniel</description>
		<content:encoded><![CDATA[<p>Hi CJ &#8211; thanks for bringing to light a few important issues:</p>
<p>1. I often assume an expert level of experience with AppleScript among the recipients of my scripts.<br />
2. The script as modified to support iTerm makes it so you *have* to have iTerm. That&#8217;s no good!</p>
<p>I will fix the iTerm problem ASAP. In the mean time, one thing you can do is just pick *any* application on your computer when it asks for iTerm.  In fact, probably just pick Terminal.  It will then mess up the script for iTerm, but should leave it working fine for Terminal.</p>
<p>The question as to where scripts should be installed is somewhat complicated, because different &#8220;script runners&#8221; look for scripts in different places. However, the most standardized location is that used by Apple&#8217;s Script Menu. This location is under the &#8220;Library&#8221; folder in a folder called &#8220;Scripts&#8221;. For instance:</p>
<p>~/Library/Scripts/</p>
<p>If you install my FastScripts utility you can use it to locate and/or create global and application-specific script folders using this convention. The scripts will be accesible from Apple&#8217;s script menu, FastScripts, and a number of other applications out there.</p>
<p>Note that to make this script really useful, you&#8217;ll want to hook it up to a keyboard shortcut. FastScripts is also an excellent choice for accomplishing this.</p>
<p>Thanks for the comments,<br />
Daniel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CJ</title>
		<link>http://www.red-sweater.com/blog/68/kids-in-the-park/comment-page-1#comment-401</link>
		<dc:creator>CJ</dc:creator>
		<pubDate>Sun, 25 Dec 2005 14:12:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/?p=68#comment-401</guid>
		<description>I tried downloading “Terminal At Selection” because I need it -- I know about &quot;open .&quot; in Terminal (to open the current directory in the Finder) but I often need the reverse function and typing all those escapes for spaces and other characters in directory names gets old.

Unfortunately, it came with no instructions as to where to place the script, and -- should there have been instructions in the script itself -- Script Editor refuses to open the script because I don&#039;t have iTerm.  Every time I try to open the script I get a dialog box asking me to locate iTerm,  the only choices being Browse and Cancel.  I think it&#039;s reasonable for me to balk at locating and installing iTerm in hopes of finding hypothetical instructions that may or may not be located in the script so I can use it.  And in fact I cracked the script open with Text Wrangler and there are no instructions.

So:

1) Where do I install the script?
2) How do I use it without installing iTerm?

[Further meta-usage note: Thanks so much for explicitly designating the required fields in yr comment form.  I&#039;m pretty freaking tired of losing submitted comments elsewhere when the required fields aren&#039;t marked.]</description>
		<content:encoded><![CDATA[<p>I tried downloading “Terminal At Selection” because I need it &#8212; I know about &#8220;open .&#8221; in Terminal (to open the current directory in the Finder) but I often need the reverse function and typing all those escapes for spaces and other characters in directory names gets old.</p>
<p>Unfortunately, it came with no instructions as to where to place the script, and &#8212; should there have been instructions in the script itself &#8212; Script Editor refuses to open the script because I don&#8217;t have iTerm.  Every time I try to open the script I get a dialog box asking me to locate iTerm,  the only choices being Browse and Cancel.  I think it&#8217;s reasonable for me to balk at locating and installing iTerm in hopes of finding hypothetical instructions that may or may not be located in the script so I can use it.  And in fact I cracked the script open with Text Wrangler and there are no instructions.</p>
<p>So:</p>
<p>1) Where do I install the script?<br />
2) How do I use it without installing iTerm?</p>
<p>[Further meta-usage note: Thanks so much for explicitly designating the required fields in yr comment form.  I'm pretty freaking tired of losing submitted comments elsewhere when the required fields aren't marked.]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

