| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| Microsoft.PowerShell.Core | About Prompts (5.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/About/about_Prompts.md | --- description: Describes the `Prompt` function and demonstrates how to create a custom `Prompt` function. Locale: en-US Previously updated : 04/15/2020 Last updated : 01/26/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_prompts?view=powershell-5.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Prompts PS C:\ps-test> ``` If you are in a nested prompt, the function adds two angle brackets (`>>`) to-the prompt. (You are in a nested prompt if the value of the -`$NestedPromptLevel` automatic variable is greater than 1.) +the prompt. You are in a nested prompt if the value of the `$NestedPromptLevel` +automatic variable is greater than 0. For example, when you are debugging in a nested prompt, the prompt resembles the following prompt: |
| Microsoft.PowerShell.Core | About Wildcards (5.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/About/about_Wildcards.md | --- description: Describes how to use wildcard characters in PowerShell. Locale: en-US Previously updated : 02/13/2021 Last updated : 01/26/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_wildcards?view=powershell-5.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Wildcards information, see [about_Regular_Expressions](./about_Regular_Expressions.md). PowerShell supports the following wildcard characters: -|Wildcard|Description |Example |Match |No Match| -|--------|--------------------------|--------|-------------|--------| -|\* |Match zero or more characters | a\* | aA, ag, Apple | banana | -|? |Match one character in that position | ?n | an, in, on | ran | -|\[ \] |Match a range of characters | \[a-l\]ook | book, cook, look | took | -|\[ \] |Match specific characters | \[bc\]ook | book, cook | hook | +| Wildcard | Description | Example | Match | No Match | +| -------- | ----------------------------------------------------------- | ----------- | ---------------- | -------- | +| `*` | Match zero or more characters | `a*` | aA, ag, Apple | banana | +| `?` | Match one character in that position | `?n` | an, in, on | ran | +| `[ ]` | Match a range of characters | `[a-l\]ook` | book, cook, look | took | +| `[ ]` | Match specific characters | `[bc]ook` | book, cook | hook | +| `` `* `` | Match any character as a literal (not a wildcard character) | ``12`*4`` | 12*4 | 1234 | You can include multiple wildcard characters in the same word pattern. For example, to find text files with names that begin with the letters **a** through **l**, type: Get-ChildItem C:\Techdocs\[a-l]*.txt ``` +There may be cases where you want to match the literal character rather than +treat it as a wildcard character. In those cases you can use the backtick +(`` ` ``) character to escape the wildcard character so that it is compared +using the literal character value. For example, ``'*hello`?*'`` matches strings +containing "hello?". + Many cmdlets accept wildcard characters in parameter values. The Help topic for each cmdlet describes which parameters accept wildcard characters. For parameters that accept wildcard characters, their use is case-insensitive. |
| Microsoft.PowerShell.Core | About Prompts (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Prompts.md | --- description: Describes the `Prompt` function and demonstrates how to create a custom `Prompt` function. Locale: en-US Previously updated : 04/15/2020 Last updated : 01/26/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_prompts?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Prompts PS C:\ps-test> ``` If you are in a nested prompt, the function adds two angle brackets (`>>`) to-the prompt. (You are in a nested prompt if the value of the -`$NestedPromptLevel` automatic variable is greater than 1.) +the prompt. You are in a nested prompt if the value of the `$NestedPromptLevel` +automatic variable is greater than 0. For example, when you are debugging in a nested prompt, the prompt resembles the following prompt: |
| Microsoft.PowerShell.Core | About Wildcards (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Wildcards.md | --- description: Describes how to use wildcard characters in PowerShell. Locale: en-US Previously updated : 02/13/2021 Last updated : 01/26/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_wildcards?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Wildcards information, see [about_Regular_Expressions](./about_Regular_Expressions.md). PowerShell supports the following wildcard characters: -|Wildcard|Description |Example |Match |No Match| -|--------|--------------------------|--------|-------------|--------| -|\* |Match zero or more characters | a\* | aA, ag, Apple | banana | -|? |Match one character in that position | ?n | an, in, on | ran | -|\[ \] |Match a range of characters | \[a-l\]ook | book, cook, look | took | -|\[ \] |Match specific characters | \[bc\]ook | book, cook | hook | +| Wildcard | Description | Example | Match | No Match | +| -------- | ----------------------------------------------------------- | ----------- | ---------------- | -------- | +| `*` | Match zero or more characters | `a*` | aA, ag, Apple | banana | +| `?` | Match one character in that position | `?n` | an, in, on | ran | +| `[ ]` | Match a range of characters | `[a-l\]ook` | book, cook, look | took | +| `[ ]` | Match specific characters | `[bc]ook` | book, cook | hook | +| `` `* `` | Match any character as a literal (not a wildcard character) | ``12`*4`` | 12*4 | 1234 | You can include multiple wildcard characters in the same word pattern. For example, to find text files with names that begin with the letters **a** through **l**, type: Get-ChildItem C:\Techdocs\[a-l]*.txt ``` +There may be cases where you want to match the literal character rather than +treat it as a wildcard character. In those cases you can use the backtick +(`` ` ``) character to escape the wildcard character so that it is compared +using the literal character value. For example, ``'*hello`?*'`` matches strings +containing "hello?". + Many cmdlets accept wildcard characters in parameter values. The Help topic for each cmdlet describes which parameters accept wildcard characters. For parameters that accept wildcard characters, their use is case-insensitive. |
| Microsoft.PowerShell.Core | About Prompts (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Prompts.md | --- description: Describes the `Prompt` function and demonstrates how to create a custom `Prompt` function. Locale: en-US Previously updated : 04/15/2020 Last updated : 01/26/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_prompts?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Prompts PS C:\ps-test> ``` If you are in a nested prompt, the function adds two angle brackets (`>>`) to-the prompt. (You are in a nested prompt if the value of the -`$NestedPromptLevel` automatic variable is greater than 1.) +the prompt. You are in a nested prompt if the value of the `$NestedPromptLevel` +automatic variable is greater than 0. For example, when you are debugging in a nested prompt, the prompt resembles the following prompt: profiles. For more information about profiles, see [about_Profiles](about_Profil [about_Debuggers](about_Debuggers.md) [about_Automatic_Variables](about_Automatic_Variables.md)- |
| Microsoft.PowerShell.Core | About Wildcards (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Wildcards.md | --- description: Describes how to use wildcard characters in PowerShell. Locale: en-US Previously updated : 02/13/2021 Last updated : 01/26/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_wildcards?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Wildcards information, see [about_Regular_Expressions](./about_Regular_Expressions.md). PowerShell supports the following wildcard characters: -|Wildcard|Description |Example |Match |No Match| -|--------|--------------------------|--------|-------------|--------| -|\* |Match zero or more characters | a\* | aA, ag, Apple | banana | -|? |Match one character in that position | ?n | an, in, on | ran | -|\[ \] |Match a range of characters | \[a-l\]ook | book, cook, look | took | -|\[ \] |Match specific characters | \[bc\]ook | book, cook | hook | +| Wildcard | Description | Example | Match | No Match | +| -------- | ----------------------------------------------------------- | ----------- | ---------------- | -------- | +| `*` | Match zero or more characters | `a*` | aA, ag, Apple | banana | +| `?` | Match one character in that position | `?n` | an, in, on | ran | +| `[ ]` | Match a range of characters | `[a-l\]ook` | book, cook, look | took | +| `[ ]` | Match specific characters | `[bc]ook` | book, cook | hook | +| `` `* `` | Match any character as a literal (not a wildcard character) | ``12`*4`` | 12*4 | 1234 | You can include multiple wildcard characters in the same word pattern. For example, to find text files with names that begin with the letters **a** through **l**, type: Get-ChildItem C:\Techdocs\[a-l]*.txt ``` +There may be cases where you want to match the literal character rather than +treat it as a wildcard character. In those cases you can use the backtick +(`` ` ``) character to escape the wildcard character so that it is compared +using the literal character value. For example, ``'*hello`?*'`` matches strings +containing "hello?". + Many cmdlets accept wildcard characters in parameter values. The Help topic for each cmdlet describes which parameters accept wildcard characters. For parameters that accept wildcard characters, their use is case-insensitive. |
| Microsoft.PowerShell.Core | About Prompts (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Prompts.md | --- description: Describes the `Prompt` function and demonstrates how to create a custom `Prompt` function. Locale: en-US Previously updated : 04/15/2020 Last updated : 01/26/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_prompts?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Prompts PS C:\ps-test> ``` If you are in a nested prompt, the function adds two angle brackets (`>>`) to-the prompt. (You are in a nested prompt if the value of the -`$NestedPromptLevel` automatic variable is greater than 1.) +the prompt. You are in a nested prompt if the value of the `$NestedPromptLevel` +automatic variable is greater than 0. For example, when you are debugging in a nested prompt, the prompt resembles the following prompt: profiles. For more information about profiles, see [about_Profiles](about_Profil [about_Debuggers](about_Debuggers.md) [about_Automatic_Variables](about_Automatic_Variables.md)- |
| Microsoft.PowerShell.Core | About Wildcards (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Wildcards.md | --- description: Describes how to use wildcard characters in PowerShell. Locale: en-US Previously updated : 02/13/2021 Last updated : 01/26/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_wildcards?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Wildcards information, see [about_Regular_Expressions](./about_Regular_Expressions.md). PowerShell supports the following wildcard characters: -|Wildcard|Description |Example |Match |No Match| -|--------|--------------------------|--------|-------------|--------| -|\* |Match zero or more characters | a\* | aA, ag, Apple | banana | -|? |Match one character in that position | ?n | an, in, on | ran | -|\[ \] |Match a range of characters | \[a-l\]ook | book, cook, look | took | -|\[ \] |Match specific characters | \[bc\]ook | book, cook | hook | +| Wildcard | Description | Example | Match | No Match | +| -------- | ----------------------------------------------------------- | ----------- | ---------------- | -------- | +| `*` | Match zero or more characters | `a*` | aA, ag, Apple | banana | +| `?` | Match one character in that position | `?n` | an, in, on | ran | +| `[ ]` | Match a range of characters | `[a-l\]ook` | book, cook, look | took | +| `[ ]` | Match specific characters | `[bc]ook` | book, cook | hook | +| `` `* `` | Match any character as a literal (not a wildcard character) | ``12`*4`` | 12*4 | 1234 | You can include multiple wildcard characters in the same word pattern. For example, to find text files with names that begin with the letters **a** through **l**, type: Get-ChildItem C:\Techdocs\[a-l]*.txt ``` +There may be cases where you want to match the literal character rather than +treat it as a wildcard character. In those cases you can use the backtick +(`` ` ``) character to escape the wildcard character so that it is compared +using the literal character value. For example, ``'*hello`?*'`` matches strings +containing "hello?". + Many cmdlets accept wildcard characters in parameter values. The Help topic for each cmdlet describes which parameters accept wildcard characters. For parameters that accept wildcard characters, their use is case-insensitive. foreach ($point in $p) { [about_If](about_If.md) [about_Script_Blocks](about_Script_Blocks.md)- |
| Microsoft.PowerShell.Core | About Prompts (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Prompts.md | --- description: Describes the `Prompt` function and demonstrates how to create a custom `Prompt` function. Locale: en-US Previously updated : 04/15/2020 Last updated : 01/26/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_prompts?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Prompts PS C:\ps-test> ``` If you are in a nested prompt, the function adds two angle brackets (`>>`) to-the prompt. (You are in a nested prompt if the value of the -`$NestedPromptLevel` automatic variable is greater than 1.) +the prompt. You are in a nested prompt if the value of the `$NestedPromptLevel` +automatic variable is greater than 0. For example, when you are debugging in a nested prompt, the prompt resembles the following prompt: profiles. For more information about profiles, see [about_Profiles](about_Profil [about_Debuggers](about_Debuggers.md) [about_Automatic_Variables](about_Automatic_Variables.md)- |
| Microsoft.PowerShell.Core | About Wildcards (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Wildcards.md | --- description: Describes how to use wildcard characters in PowerShell. Locale: en-US Previously updated : 02/13/2021 Last updated : 01/26/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_wildcards?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Wildcards information, see [about_Regular_Expressions](./about_Regular_Expressions.md). PowerShell supports the following wildcard characters: -|Wildcard|Description |Example |Match |No Match| -|--------|--------------------------|--------|-------------|--------| -|\* |Match zero or more characters | a\* | aA, ag, Apple | banana | -|? |Match one character in that position | ?n | an, in, on | ran | -|\[ \] |Match a range of characters | \[a-l\]ook | book, cook, look | took | -|\[ \] |Match specific characters | \[bc\]ook | book, cook | hook | +| Wildcard | Description | Example | Match | No Match | +| -------- | ----------------------------------------------------------- | ----------- | ---------------- | -------- | +| `*` | Match zero or more characters | `a*` | aA, ag, Apple | banana | +| `?` | Match one character in that position | `?n` | an, in, on | ran | +| `[ ]` | Match a range of characters | `[a-l\]ook` | book, cook, look | took | +| `[ ]` | Match specific characters | `[bc]ook` | book, cook | hook | +| `` `* `` | Match any character as a literal (not a wildcard character) | ``12`*4`` | 12*4 | 1234 | You can include multiple wildcard characters in the same word pattern. For example, to find text files with names that begin with the letters **a** through **l**, type: Get-ChildItem C:\Techdocs\[a-l]*.txt ``` +There may be cases where you want to match the literal character rather than +treat it as a wildcard character. In those cases you can use the backtick +(`` ` ``) character to escape the wildcard character so that it is compared +using the literal character value. For example, ``'*hello`?*'`` matches strings +containing "hello?". + Many cmdlets accept wildcard characters in parameter values. The Help topic for each cmdlet describes which parameters accept wildcard characters. For parameters that accept wildcard characters, their use is case-insensitive. foreach ($point in $p) { [about_If](about_If.md) [about_Script_Blocks](about_Script_Blocks.md)- |