If you attempt tab completion on a file in a subdirectory of the current one
(eg, sub<tab>\fi<tab> for subdir\file), PoSH autocompletes the full path.
C:\a\long\path\with\many\subdirectories\file.txt



This is annoying when the path actually is really long, like 90 characters
long. It should be more like cmd.exe's autocompletion, which does not expand
into the full path.

"Adam Milazzo [MSFT]" <adamm@san.rr.com> wrote in message
news:%2396zNGbvGHA.1372@TK2MSFTNGP04.phx.gbl...
> If you attempt tab completion on a file in a subdirectory of the current
> one (eg, sub<tab>\fi<tab> for subdir\file), PoSH autocompletes the full
> path.
> C:\a\long\path\with\many\subdirectories\file.txt
>
> This is annoying when the path actually is really long, like 90 characters
> long. It should be more like cmd.exe's autocompletion, which does not
> expand into the full path.

I 100% agree with you on this. I've bugged it before. Now it might be nice
to have a way to get PoSH to autocomplete and give the full path but I don't
think it should be via the default TAB shortcut (maybe Ctrl+TAB instead).

--
Keith

Keith Hill [MVP] wrote:
> "Adam Milazzo [MSFT]" <adamm@san.rr.com> wrote in message
> news:%2396zNGbvGHA.1372@TK2MSFTNGP04.phx.gbl...
>> This is annoying when the path actually is really long, like 90
>> characters long. It should be more like cmd.exe's autocompletion,
>> which does not expand into the full path.
>
> I 100% agree with you on this. I've bugged it before. Now it might be
> nice to have a way to get PoSH to autocomplete and give the full path
> but I don't think it should be via the default TAB shortcut (maybe
> Ctrl+TAB instead).

I think the cases where the full path is really needed are rare, and you
could get away with defining a function that takes a possibly-relative
path and returns the full path.