From c3b03065bfc1ff06e2d77ef437bf6f1bffd06248 Mon Sep 17 00:00:00 2001 From: Sean Wheeler Date: Mon, 16 May 2022 16:33:56 -0500 Subject: [PATCH] Fix broken bookmark (#8822) --- .../5.1/Microsoft.PowerShell.Core/About/about_Parsing.md | 6 ++++-- .../7.0/Microsoft.PowerShell.Core/About/about_Parsing.md | 6 ++++-- .../7.1/Microsoft.PowerShell.Core/About/about_Parsing.md | 6 ++++-- .../7.2/Microsoft.PowerShell.Core/About/about_Parsing.md | 6 ++++-- .../7.3/Microsoft.PowerShell.Core/About/about_Parsing.md | 6 ++++-- 5 files changed, 20 insertions(+), 10 deletions(-) diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/about_Parsing.md b/reference/5.1/Microsoft.PowerShell.Core/About/about_Parsing.md index 3119abda88f..4fd68546e9f 100644 --- a/reference/5.1/Microsoft.PowerShell.Core/About/about_Parsing.md +++ b/reference/5.1/Microsoft.PowerShell.Core/About/about_Parsing.md @@ -200,8 +200,6 @@ prevent PowerShell from misinterpreting the parentheses. icacls X:\VMS /grant Dom\HVAdmin:`(CI`)`(OI`)F ``` -### The stop-parsing and end-of-parameters tokens - Beginning in PowerShell 3.0, you can use the _stop-parsing_ (`--%`) and _end-of-parameters_ tokens (`--`) to stop PowerShell from interpreting input as PowerShell commands or expressions. @@ -209,6 +207,8 @@ PowerShell commands or expressions. > [!NOTE] > The stop-parsing token is only intended for use on Windows platforms. +### The stop-parsing token + When calling a native command, place the stop-parsing token before the program arguments. This technique is much easier than using escape characters to prevent misinterpretation. @@ -239,6 +239,8 @@ variable the token is passed through as-is. You cannot use stream redirection (like `>file.txt`) because they are passed verbatim as arguments to the target command. +### The end-of-parameters token + The end-of-parameters token (`--`) indicates that all arguments following it are to be passed in their actual form as though double quotes were placed around them. For example, using `--` you can output the string `-InputObject` diff --git a/reference/7.0/Microsoft.PowerShell.Core/About/about_Parsing.md b/reference/7.0/Microsoft.PowerShell.Core/About/about_Parsing.md index b2449f36904..c15fb9099f4 100644 --- a/reference/7.0/Microsoft.PowerShell.Core/About/about_Parsing.md +++ b/reference/7.0/Microsoft.PowerShell.Core/About/about_Parsing.md @@ -200,8 +200,6 @@ prevent PowerShell from misinterpreting the parentheses. icacls X:\VMS /grant Dom\HVAdmin:`(CI`)`(OI`)F ``` -### The stop-parsing and end-of-parameters tokens - Beginning in PowerShell 3.0, you can use the _stop-parsing_ (`--%`) and _end-of-parameters_ tokens (`--`) to stop PowerShell from interpreting input as PowerShell commands or expressions. @@ -209,6 +207,8 @@ PowerShell commands or expressions. > [!NOTE] > The stop-parsing token is only intended for use on Windows platforms. +### The stop-parsing token + When calling a native command, place the stop-parsing token before the program arguments. This technique is much easier than using escape characters to prevent misinterpretation. @@ -239,6 +239,8 @@ variable the token is passed through as-is. You cannot use stream redirection (like `>file.txt`) because they are passed verbatim as arguments to the target command. +### The end-of-parameters token + The end-of-parameters token (`--`) indicates that all arguments following it are to be passed in their actual form as though double quotes were placed around them. For example, using `--` you can output the string `-InputObject` diff --git a/reference/7.1/Microsoft.PowerShell.Core/About/about_Parsing.md b/reference/7.1/Microsoft.PowerShell.Core/About/about_Parsing.md index 9f780839b2e..27673c04cdd 100644 --- a/reference/7.1/Microsoft.PowerShell.Core/About/about_Parsing.md +++ b/reference/7.1/Microsoft.PowerShell.Core/About/about_Parsing.md @@ -200,8 +200,6 @@ prevent PowerShell from misinterpreting the parentheses. icacls X:\VMS /grant Dom\HVAdmin:`(CI`)`(OI`)F ``` -### The stop-parsing and end-of-parameters tokens - Beginning in PowerShell 3.0, you can use the _stop-parsing_ (`--%`) and _end-of-parameters_ tokens (`--`) to stop PowerShell from interpreting input as PowerShell commands or expressions. @@ -209,6 +207,8 @@ PowerShell commands or expressions. > [!NOTE] > The stop-parsing token is only intended for use on Windows platforms. +### The stop-parsing token + When calling a native command, place the stop-parsing token before the program arguments. This technique is much easier than using escape characters to prevent misinterpretation. @@ -239,6 +239,8 @@ variable the token is passed through as-is. You cannot use stream redirection (like `>file.txt`) because they are passed verbatim as arguments to the target command. +### The end-of-parameters token + The end-of-parameters token (`--`) indicates that all arguments following it are to be passed in their actual form as though double quotes were placed around them. For example, using `--` you can output the string `-InputObject` diff --git a/reference/7.2/Microsoft.PowerShell.Core/About/about_Parsing.md b/reference/7.2/Microsoft.PowerShell.Core/About/about_Parsing.md index 6350a22a74d..c989823195a 100644 --- a/reference/7.2/Microsoft.PowerShell.Core/About/about_Parsing.md +++ b/reference/7.2/Microsoft.PowerShell.Core/About/about_Parsing.md @@ -200,8 +200,6 @@ prevent PowerShell from misinterpreting the parentheses. icacls X:\VMS /grant Dom\HVAdmin:`(CI`)`(OI`)F ``` -### The stop-parsing and end-of-parameters tokens - Beginning in PowerShell 3.0, you can use the _stop-parsing_ (`--%`) and _end-of-parameters_ tokens (`--`) to stop PowerShell from interpreting input as PowerShell commands or expressions. @@ -209,6 +207,8 @@ PowerShell commands or expressions. > [!NOTE] > The stop-parsing token is only intended for use on Windows platforms. +### The stop-parsing token + When calling a native command, place the stop-parsing token before the program arguments. This technique is much easier than using escape characters to prevent misinterpretation. @@ -239,6 +239,8 @@ variable the token is passed through as-is. You cannot use stream redirection (like `>file.txt`) because they are passed verbatim as arguments to the target command. +### The end-of-parameters token + The end-of-parameters token (`--`) indicates that all arguments following it are to be passed in their actual form as though double quotes were placed around them. For example, using `--` you can output the string `-InputObject` diff --git a/reference/7.3/Microsoft.PowerShell.Core/About/about_Parsing.md b/reference/7.3/Microsoft.PowerShell.Core/About/about_Parsing.md index f60dab6dafd..f417b8d3754 100644 --- a/reference/7.3/Microsoft.PowerShell.Core/About/about_Parsing.md +++ b/reference/7.3/Microsoft.PowerShell.Core/About/about_Parsing.md @@ -200,8 +200,6 @@ prevent PowerShell from misinterpreting the parentheses. icacls X:\VMS /grant Dom\HVAdmin:`(CI`)`(OI`)F ``` -### The stop-parsing and end-of-parameters tokens - Beginning in PowerShell 3.0, you can use the _stop-parsing_ (`--%`) and _end-of-parameters_ tokens (`--`) to stop PowerShell from interpreting input as PowerShell commands or expressions. @@ -209,6 +207,8 @@ PowerShell commands or expressions. > [!NOTE] > The stop-parsing token is only intended for use on Windows platforms. +### The stop-parsing token + When calling a native command, place the stop-parsing token before the program arguments. This technique is much easier than using escape characters to prevent misinterpretation. @@ -239,6 +239,8 @@ variable the token is passed through as-is. You cannot use stream redirection (like `>file.txt`) because they are passed verbatim as arguments to the target command. +### The end-of-parameters token + The end-of-parameters token (`--`) indicates that all arguments following it are to be passed in their actual form as though double quotes were placed around them. For example, using `--` you can output the string `-InputObject`