Windows PowerShell 1.0 String Quoting and Escape Sequences - Revision history

Neil: Text replacement - " " to "
"
2016-10-27T20:14:38Z
Text replacement - "<table border="0" cellspacing="0"> " to "<table border="0" cellspacing="0" width="100%">"

← Older revision Revision as of 20:14, 27 October 2016
Line 1: Line 1:

−
<table border="0" cellspacing="0">
+
<table border="0" cellspacing="0" width="100%"><tr>

−
<tr>
+

<td width="20%">[[Windows PowerShell 1.0 Commands and Aliases|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Directing and Formatting Windows PowerShell 1.0 Output|Next]]</td>

<td width="20%">[[Windows PowerShell 1.0 Commands and Aliases|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Directing and Formatting Windows PowerShell 1.0 Output|Next]]</td>

<tr>

<tr>

Neil: Text replacement - "" to "
"
2016-05-05T14:43:56Z
Text replacement - "<table border="0" cellspacing="0" width="100%">" to "<table border="0" cellspacing="0">"

← Older revision Revision as of 14:43, 5 May 2016
Line 1: Line 1:

−
<table border="0" cellspacing="0" width="100%">
+
<table border="0" cellspacing="0">

<tr>

<tr>

<td width="20%">[[Windows PowerShell 1.0 Commands and Aliases|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Directing and Formatting Windows PowerShell 1.0 Output|Next]]</td>

<td width="20%">[[Windows PowerShell 1.0 Commands and Aliases|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Directing and Formatting Windows PowerShell 1.0 Output|Next]]</td>

Neil: Text replacement - "BUY_WPS" to "powershell"

2016-02-01T21:12:12Z

Text replacement - "<google>BUY_WPS</google>" to "<htmlet>powershell</htmlet>"

Neil at 19:00, 14 May 2009

2009-05-14T19:00:28Z

Neil at 13:34, 14 May 2009

2009-05-14T13:34:24Z

Neil: /* PowerShell Special Escape Sequences */

2009-03-18T18:09:25Z

‎PowerShell Special Escape Sequences

Neil: /* Using the PowerShell Escape Character */

2009-03-18T18:08:02Z

‎Using the PowerShell Escape Character

Neil: /* Using the PowerShell Escape Character */

2009-03-18T18:07:32Z

‎Using the PowerShell Escape Character

Neil: /* Using Double Quotes */

2009-03-18T18:07:12Z

‎Using Double Quotes

Neil: /* Using Double Quotes */

2009-03-18T18:06:03Z

‎Using Double Quotes

← Older revision		Revision as of 21:12, 1 February 2016
Line 8:		Line 8:


−	<~~google~~>~~BUY_WPS~~</~~google~~>	+	<htmlet>powershell</htmlet>

@@ Line 11: / Line 11: @@
-A key requirements of any command line shell or scripting language involves gaining an understanding of using quotation marks to encapsulate strings and escape sequences to enter special characters such as newlines or carriage returns. As Windows PowerShell is no exception to this rule, the objective of this chapter is provide a detailed overview of the different techniques for quoting and escaping strings and characters.
+A key requirement of any command line shell or scripting language involves gaining an understanding of using quotation marks to encapsulate strings and escape sequences to enter special characters such as newlines or carriage returns. As Windows PowerShell is no exception to this rule, the objective of this chapter is provide a detailed overview of the different techniques for quoting and escaping strings and characters.
 == Using Double Quotes ==
@@ Line 61: / Line 61: @@
 </pre>
-Both these problems may be alleviated using single quotes or by escaping, both of which are covered in the following sections.
+Both these problems may be alleviated either by using single quotes or by escaping, both of which are covered in the following sections.
 == Using Single Quotes ==
@@ Line 80: / Line 80: @@
 </pre>
-In fact, anything placed inside single quotes is taken literally, with the expection of other single quotes which cause a problem similar to the use of doublke quotes in a double quoted string. For example:
+In fact, anything placed inside single quotes is taken literally, with the expection of other single quotes which cause a problem similar to the use of double quotes in a double quoted string. For example:
 <pre>
@@ Line 100: / Line 100: @@
 == Using the PowerShell Escape Character ==
-The PowerShell escape character takes the form of a back quote (`) and instructs PowerShell to treat the following character literally, as opposed to interpreting it in some other way. Those familiar with other shells and programming languages will be more familiar with using the back slash character (\) for escaping. The reason for the use of the back quote instead of the backslash is the direct result of the decision in the first version of DOS to use the backslash character to separate the different parts of a file path, for example ''C:\Windows\Program Files''. Other than this difference, but the concept of escaping is otherwise the same.
+The PowerShell escape character takes the form of a back quote (`) and instructs PowerShell to treat the following character literally, as opposed to interpreting it in some other way. Those familiar with other shells and programming languages will be more familiar with using the back slash character (\) for escaping. The reason for the use of the back quote instead of the backslash is the direct result of the decision in the first version of DOS to use the backslash character to separate the different parts of a file path, for example ''C:\Windows\Program Files''. Other than this difference, the concept of escaping is otherwise the same.
 To understand the escape character, consider the first example in this chapter, whereby PowerShell interpreted the second word after the ''-inputobject'' paramater as an additional argument:
@@ Line 132: / Line 132: @@
 </pre>
-The trick to including a back quote in a string and not have it treated as an escape character is to escape the back quote itself, in other words typing it was ``:
+The trick to including a back quote in a string and not have it treated as an escape character is to escape the back quote itself, in other words typing it as ``:
 <pre>
@@ Line 143: / Line 143: @@
 == PowerShell Special Escape Sequences ==
-Escape sequences are involve the use of the back quote escape together with one other character to represent a special character that cannot otherwise be represented in a string. For example, a tab or new line. The following table lists the special escape sequences supported by Windows PowerShell:
+Escape sequences involve the use of the back quote escape together with one other character to represent a special character that cannot otherwise be represented in a string. For example, a tab or new line. The following table lists the special escape sequences supported by Windows PowerShell:
 <google>ADSDAQBOX_FLOW</google>
 <table border="1" cellpadding="5" cellspacing="0" id="E3B" style="border-collapse: collapse; border-color:#cccccc; border-style: solid; border-width: 1px; margin-bottom:20px">
@@ Line 244: / Line 244: @@
 This is line 2
 </pre>

@@ Line 132: / Line 132: @@
 Escape sequences are involve the use of the back quote escape together with one other character to represent a special character that cannot otherwise be represented in a string. For example, a tab or new line. The following table lists the special escape sequences supported by Windows PowerShell:
+<google>ADSDAQBOX_FLOW</google>
 <table border="1" cellpadding="5" cellspacing="0" id="E3B" style="border-collapse: collapse; border-color:#cccccc; border-style: solid; border-width: 1px; margin-bottom:20px">
 <tr bgcolor="#cccccc" style="color:black" valign="top">

@@ Line 87: / Line 87: @@
 == Using the PowerShell Escape Character ==
-<google>ADSDAQBOX_FLOW</google>
 The PowerShell escape character takes the form of a back quote (`) and instructs PowerShell to treat the following character literally, as opposed to interpreting it in some other way. Those familiar with other shells and programming languages will be more familiar with using the back slash character (\) for escaping. The reason for the use of the back quote instead of the backslash is the direct result of the decision in the first version of DOS to use the backslash character to separate the different parts of a file path, for example ''C:\Windows\Program Files''. Other than this difference, but the concept of escaping is otherwise the same.

@@ Line 87: / Line 87: @@
 == Using the PowerShell Escape Character ==
+<google>ADSDAQBOX_FLOW</google>
 The PowerShell escape character takes the form of a back quote (`) and instructs PowerShell to treat the following character literally, as opposed to interpreting it in some other way. Those familiar with other shells and programming languages will be more familiar with using the back slash character (\) for escaping. The reason for the use of the back quote instead of the backslash is the direct result of the decision in the first version of DOS to use the backslash character to separate the different parts of a file path, for example ''C:\Windows\Program Files''. Other than this difference, but the concept of escaping is otherwise the same.

@@ Line 1: / Line 1: @@
-<table border="0" cellspacing="0">
+<table border="0" cellspacing="0" width="100%"><tr>
 <tr>
 <td width="20%">[[Windows PowerShell 1.0 Commands and Aliases|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Directing and Formatting Windows PowerShell 1.0 Output|Next]]</td>
 <tr>

← Older revision		Revision as of 13:34, 14 May 2009
Line 1:		Line 1:
		+	<table border="0" cellspacing="0" width="100%">
		+	<tr>
		+	<td width="20%">[[Windows PowerShell 1.0 Commands and Aliases\|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials\|Table of Contents]]<td width="20%" align="right">[[Directing and Formatting Windows PowerShell 1.0 Output\|Next]]</td>
		+	<tr>
		+	<td width="20%">Windows PowerShell 1.0 Commands and Aliases<td align="center"><td width="20%" align="right">Directing and Formatting Windows PowerShell 1.0 Output</td>
		+	</table>
		+	<hr>
		+
		+
		+	<google>BUY_WPS</google>
		+
		+
	A key requirements of any command line shell or scripting language involves gaining an understanding of using quotation marks to encapsulate strings and escape sequences to enter special characters such as newlines or carriage returns. As Windows PowerShell is no exception to this rule, the objective of this chapter is provide a detailed overview of the different techniques for quoting and escaping strings and characters.		A key requirements of any command line shell or scripting language involves gaining an understanding of using quotation marks to encapsulate strings and escape sequences to enter special characters such as newlines or carriage returns. As Windows PowerShell is no exception to this rule, the objective of this chapter is provide a detailed overview of the different techniques for quoting and escaping strings and characters.