<?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"
	>
<channel>
	<title>Comments on: Terminal scripting in 10.5</title>
	<atom:link href="http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/</link>
	<description>The Omni Mouth: standing outside your bedroom window playing \"In Your Eyes\" since 2006.</description>
	<pubDate>Mon, 13 Oct 2008 00:49:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Brian</title>
		<link>http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63766</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Fri, 16 Nov 2007 21:15:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63766</guid>
		<description>Brian: I'm seeing the same behavior in Firefox, so I think this is a blog-problem, rather than a browser-problem...</description>
		<content:encoded><![CDATA[<p>Brian: I&#8217;m seeing the same behavior in Firefox, so I think this is a blog-problem, rather than a browser-problem&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63748</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Mon, 05 Nov 2007 16:37:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63748</guid>
		<description>You're going to love this, but there's a display error in this blog entry in OmniWeb!  The word "hopefully" in your code block draws over the right hand border into the links section, no matter the width of the window since it looks like the columns are fixed-width. Whoops!</description>
		<content:encoded><![CDATA[<p>You&#8217;re going to love this, but there&#8217;s a display error in this blog entry in OmniWeb!  The word &#8220;hopefully&#8221; in your code block draws over the right hand border into the links section, no matter the width of the window since it looks like the columns are fixed-width. Whoops!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicholas Riley</title>
		<link>http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63746</link>
		<dc:creator>Nicholas Riley</dc:creator>
		<pubDate>Mon, 05 Nov 2007 06:45:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63746</guid>
		<description>Have you figured out how to create a new tab or window with a particular style?  I tried the following with no luck:

Good to know. Any suggestions on syntax? I can get references to windows and tabs and settings sets but not create anything.

 tell application "Terminal"

    copy (settings set "shrug (mail)") to theSet
    copy (front window) to theWindow
    make new tab at theWindow with properties {current settings:theSet}
    # Terminal got an error: Canâ€™t make or move that element into that container.
    make new tab after tab 1 of theWindow with properties {current settings:theSet}
    # Terminal got an error: Canâ€™t make tab after tab 1 of window id 9059 into type type.
 end tell</description>
		<content:encoded><![CDATA[<p>Have you figured out how to create a new tab or window with a particular style?  I tried the following with no luck:</p>
<p>Good to know. Any suggestions on syntax? I can get references to windows and tabs and settings sets but not create anything.</p>
<p> tell application &#8220;Terminal&#8221;</p>
<p>    copy (settings set &#8220;shrug (mail)&#8221;) to theSet<br />
    copy (front window) to theWindow<br />
    make new tab at theWindow with properties {current settings:theSet}<br />
    # Terminal got an error: Canâ€™t make or move that element into that container.<br />
    make new tab after tab 1 of theWindow with properties {current settings:theSet}<br />
    # Terminal got an error: Canâ€™t make tab after tab 1 of window id 9059 into type type.<br />
 end tell</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michaelgalloy.com &#187; Terminal scripting in Leopard</title>
		<link>http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63745</link>
		<dc:creator>michaelgalloy.com &#187; Terminal scripting in Leopard</dc:creator>
		<pubDate>Sun, 04 Nov 2007 21:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63745</guid>
		<description>[...] This is an interesting article about using some of the new scripting features in Leopard's Terminal to visually indicate which server you are logged into. [...]</description>
		<content:encoded><![CDATA[<p>[...] This is an interesting article about using some of the new scripting features in Leopard&#8217;s Terminal to visually indicate which server you are logged into. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DV Henkel-Wallace</title>
		<link>http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63744</link>
		<dc:creator>DV Henkel-Wallace</dc:creator>
		<pubDate>Sun, 04 Nov 2007 17:20:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63744</guid>
		<description>Why not just have your shell config files (.profile or whathaveyou) change your cmd line to be something descriptive?  I've been using the machine name followed by "% " or "# " for the past 25 years and it's served me fine).  You can even change the text color on a per-machine basis, for added user-friendliness.</description>
		<content:encoded><![CDATA[<p>Why not just have your shell config files (.profile or whathaveyou) change your cmd line to be something descriptive?  I&#8217;ve been using the machine name followed by &#8220;% &#8221; or &#8220;# &#8221; for the past 25 years and it&#8217;s served me fine).  You can even change the text color on a per-machine basis, for added user-friendliness.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leopard: scripting di Terminal.app - ReFactor.it</title>
		<link>http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63742</link>
		<dc:creator>Leopard: scripting di Terminal.app - ReFactor.it</dc:creator>
		<pubDate>Sun, 04 Nov 2007 14:17:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63742</guid>
		<description>[...] Leopard, ecco come sfruttare le migliorie alla â€œscriptabilitÃ â€? di Terminal, in questo caso per impostare lo stile per tutte le connessioni remote.  Scritto il 04/11/07 da giorgio_v. Tags: [...]</description>
		<content:encoded><![CDATA[<p>[...] Leopard, ecco come sfruttare le migliorie alla â€œscriptabilitÃ â€? di Terminal, in questo caso per impostare lo stile per tutte le connessioni remote.  Scritto il 04/11/07 da giorgio_v. Tags: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Apple Blog &#187; Terminal scripting in 10.5</title>
		<link>http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63739</link>
		<dc:creator>Apple Blog &#187; Terminal scripting in 10.5</dc:creator>
		<pubDate>Sat, 03 Nov 2007 22:20:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63739</guid>
		<description>[...] The Omni Mouth placed an observative post today on Terminal scripting in 10.5Here&#8217;s a quick excerpt Terminal in 10.5 has seen some great scripting improvements to match its additional functionality. Occasionally I have several Terminal sessions with some sshâ€˜d remote servers and then I forget which Terminals are local and which are remote. Here is a simple little command-line AppleScript that will let you set an individual Terminalâ€™s style from the command line; SetTerminalStyle.zip Put the script in your PATH somewhere and then add a ssh function in your .zshrc, or equivalent: # Show remo [...]</description>
		<content:encoded><![CDATA[<p>[...] The Omni Mouth placed an observative post today on Terminal scripting in 10.5Here&#8217;s a quick excerpt Terminal in 10.5 has seen some great scripting improvements to match its additional functionality. Occasionally I have several Terminal sessions with some sshâ€˜d remote servers and then I forget which Terminals are local and which are remote. Here is a simple little command-line AppleScript that will let you set an individual Terminalâ€™s style from the command line; SetTerminalStyle.zip Put the script in your PATH somewhere and then add a ssh function in your .zshrc, or equivalent: # Show remo [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Iphone &#124; Apple &#124; Mac Blog &#187; Terminal scripting in 10.5</title>
		<link>http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63738</link>
		<dc:creator>Iphone &#124; Apple &#124; Mac Blog &#187; Terminal scripting in 10.5</dc:creator>
		<pubDate>Sat, 03 Nov 2007 22:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63738</guid>
		<description>[...] The Omni Mouth created an interesting post today on Terminal scripting in 10.5Here&#8217;s a short outline [...]</description>
		<content:encoded><![CDATA[<p>[...] The Omni Mouth created an interesting post today on Terminal scripting in 10.5Here&#8217;s a short outline [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63737</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Sat, 03 Nov 2007 22:07:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.omnigroup.com/2007/11/03/terminal-scripting-in-105/#comment-63737</guid>
		<description>Instead of hard-coding the path to ssh, you might use
command ssh "$@"

I'd also prefer a "GetTerminalStyle" script instead of simply resetting to "default", but I'll have to wait for Leopard anyway ;-)</description>
		<content:encoded><![CDATA[<p>Instead of hard-coding the path to ssh, you might use<br />
command ssh &#8220;$@&#8221;</p>
<p>I&#8217;d also prefer a &#8220;GetTerminalStyle&#8221; script instead of simply resetting to &#8220;default&#8221;, but I&#8217;ll have to wait for Leopard anyway <img src='http://blog.omnigroup.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>
