![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
|
Welcome to Vista Forums we are your forum to discuss Windows Vista x64 and x86 systems. Whether you need help or just want to post an idea you have on Vista, this is the forum for you.
br> br> |
| |||||||
![]() |
| | Thread Tools | Display Modes |
| | #1 (permalink) |
| Guest | tabcompletion does not show : Split-Path -Leaf when I do tabcompletion in splitpath PoSH>Split-Path -[tab] Split-Path -Leaf is skipped and does not show up PoSH>Split-Path $profile -Leaf Microsoft.PowerShell_profile.ps1 PoSH>Split-Path -[tab] can someone confirm ? Greetings /\/\o\/\/ |
My System Specs![]() |
| | #2 (permalink) |
| Guest | Re: tabcompletion does not show : Split-Path -Leaf I believe that tab completion is providing the parameters from the default parameter set jim -- -- James Truher [MSFT] Windows PowerShell Development Microsoft Corporation This posting is provided "AS IS" with no warranties, and confers no rights. "/\/\o\/\/ [MVP]" <mow001@hotmail.NoSpam> wrote in message news:Ol8ZmRZ6GHA.3452@TK2MSFTNGP05.phx.gbl... > when I do tabcompletion in splitpath > > PoSH>Split-Path -[tab] > > Split-Path -Leaf is skipped and does not show up > > PoSH>Split-Path $profile -Leaf > Microsoft.PowerShell_profile.ps1 > PoSH>Split-Path -[tab] > > can someone confirm ? > > Greetings /\/\o\/\/ > |
My System Specs![]() |
| | #3 (permalink) |
| Guest | Re: tabcompletion does not show : Split-Path -Leaf If I understand correctly what "parameter set" means, it actually appears to be working its way through all the parameter sets, one at a time. If I keep hitting the tab key in MoW's example, I get the sequence shown below. (I broke it up into separate lines to show that each line corresponds to a separate parameter set in the output from "get-help split-path".) That seems like a lot of tab keys just to get a parameter from the fourth parameter set. And it doesn't seem to follow the Rule of Least Surprise. -Path -LiteralPath -Parent -Resolve -Credential -Verbose -Debug -ErrorAction -ErrorVariable -OutVariable -OutBuffer -Path -LiteralPath -Qualifer -Resolve -Credential -Verbose -Debug -Erroraction -ErrorVariable -OutVariable -OutBuffer -Path -LiteralPath -NoQualifier -Resolve -Credential -Verbose -Debug -Erroraction -ErrorVariable -OutVariable -OutBuffer -Path -LiteralPath -Leaf -Resolve -Credential -Verbose -Debug -Erroraction -ErrorVariable -OutVariable -OutBuffer -Path -LiteralPath -Resolve -IsAbsolute -Credential -Verbose -Debug -Erroraction -ErrorVariable -OutVariable -OutBuffer "James Truher" wrote: > I believe that tab completion is providing the parameters from the default > parameter set > > jim > > -- > -- > James Truher [MSFT] > Windows PowerShell Development > Microsoft Corporation > This posting is provided "AS IS" with no warranties, and confers no rights. > > "/\/\o\/\/ [MVP]" <mow001@hotmail.NoSpam> wrote in message > news:Ol8ZmRZ6GHA.3452@TK2MSFTNGP05.phx.gbl... > > when I do tabcompletion in splitpath > > > > PoSH>Split-Path -[tab] > > > > Split-Path -Leaf is skipped and does not show up > > > > PoSH>Split-Path $profile -Leaf > > Microsoft.PowerShell_profile.ps1 > > PoSH>Split-Path -[tab] > > > > can someone confirm ? > > > > Greetings /\/\o\/\/ > > > > > |
My System Specs![]() |
| | #4 (permalink) |
| Guest | Re: tabcompletion does not show : Split-Path -Leaf "Jim Holbach" <JimHolbach@discussions.microsoft.com> wrote in message news:71E718AC-EDC1-490B-B05B-94B49BEDB704@microsoft.com... > If I understand correctly what "parameter set" means, it actually appears > to > be working its way through all the parameter sets, one at a time. Jim, this is brilliant. I never realized this! ![]() |
My System Specs![]() |
| | #5 (permalink) |
| Guest | Re: tabcompletion does not show : Split-Path -Leaf To a newbie like me, it was very surprising to realize that was the behavior of the tab expansion for cmdlets. Sorry if I was pedantic in my attempt to explain my confusion. But it seems to me to be more useful (and less surprising) if the list were sorted and "uniqued" so that, for example, "split-path - [tab]" would walk you thru the abbreviated list below instead of making you tab your way thru all the "dupes" along the way? That's how I've modified my tab expansion function anyway now that I realized what it was doing. -Credential -Debug -ErrorAction -ErrorVariable -IsAbsolute -Leaf -LiteralPath -NoQualifier -OutBuffer -OutVariable -Parent -Path -Qualifier -Resolve -Verbose --- Jim Holbach "Alex K. Angelopoulos [MVP]" wrote: > "Jim Holbach" <JimHolbach@discussions.microsoft.com> wrote in message > news:71E718AC-EDC1-490B-B05B-94B49BEDB704@microsoft.com... > > If I understand correctly what "parameter set" means, it actually appears > > to > > be working its way through all the parameter sets, one at a time. > > Jim, this is brilliant. I never realized this! ![]() > > > |
My System Specs![]() |
![]() |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| split-path -> unc-path | lerni | PowerShell | 4 | 07-31-2008 04:27 AM |
| Error in help Example 4 for split-path | Dainis | PowerShell | 1 | 03-28-2007 02:00 PM |
| Error in help Example 3 for split-path | Dainis | PowerShell | 2 | 03-28-2007 01:58 PM |
| split-path doc bug | Andrew Watt [MVP] | PowerShell | 2 | 07-06-2006 02:33 AM |
| Errors in Help file for split-path | Andrew Watt [MVP] | PowerShell | 0 | 05-21-2006 02:23 PM |