<?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: Windows PowerShell Aliases</title>
	<atom:link href="http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.powershellpro.com</link>
	<description>Sharing the Experience</description>
	<pubDate>Wed, 07 Jan 2009 01:39:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Jim</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/#comment-252</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Wed, 12 Nov 2008 00:56:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-aliases/#comment-252</guid>
		<description>I don't know if having My Documents redirected to the D: drive has anything to do with it, but the Profile.ps1 results in the following for me:

Incomplete string token.
At line:1 char:14
+ . 'F:\Jim`'s D &#60;&#60;&#60;&#60; ocuments\WindowsPowerShell\profile.ps1'</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know if having My Documents redirected to the D: drive has anything to do with it, but the Profile.ps1 results in the following for me:</p>
<p>Incomplete string token.<br />
At line:1 char:14<br />
+ . &#8216;F:\Jim`&#8217;s D &lt;&lt;&lt;&lt; ocuments\WindowsPowerShell\profile.ps1&#8242;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy Pardee</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/#comment-120</link>
		<dc:creator>Roy Pardee</dc:creator>
		<pubDate>Fri, 30 May 2008 22:13:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-aliases/#comment-120</guid>
		<description>Ach--thanks Kevin!  I've been surfing around for a while now looking for multi-word examples &#38; trying different combinations of single/double quotes &#38; escapes &#38; such and having no luck.

I guess it's *functions* that I need to be able to do multi-word commands?</description>
		<content:encoded><![CDATA[<p>Ach&#8211;thanks Kevin!  I&#8217;ve been surfing around for a while now looking for multi-word examples &amp; trying different combinations of single/double quotes &amp; escapes &amp; such and having no luck.</p>
<p>I guess it&#8217;s *functions* that I need to be able to do multi-word commands?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Kelleher</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/#comment-25</link>
		<dc:creator>Kevin Kelleher</dc:creator>
		<pubDate>Mon, 05 Nov 2007 15:45:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-aliases/#comment-25</guid>
		<description>I think it would be helpful for those us with a unix background to make it clear that PowerScript aliases are aliases for single words.  I didn't realize this at first, and couldn't understand why I couldn't redefine "ls" as "get-childitem -force -name".</description>
		<content:encoded><![CDATA[<p>I think it would be helpful for those us with a unix background to make it clear that PowerScript aliases are aliases for single words.  I didn&#8217;t realize this at first, and couldn&#8217;t understand why I couldn&#8217;t redefine &#8220;ls&#8221; as &#8220;get-childitem -force -name&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
