Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Done Temporarily Disabling Aliases

Aug
1,978
73
Before I visit feedback to post for an enhancement, I would like to see if others feel this would be a worthwhile enhancement.

If I have an alias called pwd, but I also have a command pwd, of course I can
Code:
*pwd
to run the command instead of the alias.

Also, if I do
Code:
which /a pwd
it shows that the alias is used first instead of the command.

No problem so far.

I would like to have the which command be able to display the command that would be executed if I were to disable the alias, for example
Code:
which *pid

As of now, if I use which pwd or which *pwd it always returns that it is an alias.

Joe
 
That sounds like a sensible behavior. But note that you can see both at once with WHICH /A.
 
You can also specify the extension if you know what it is.
Code:
[C:\] which /a subst
subst is an alias : "C:\TC17\psubst.btm"
subst is an external : C:\Windows\system32\subst.exe

[C:\] which subst.exe
subst.exe is an external : C:\Windows\system32\subst.exe
 
You can also specify the extension if you know what it is.
Code:
[C:\] which /a subst
subst is an alias : "C:\TC17\psubst.btm"
subst is an external : C:\Windows\system32\subst.exe

[C:\] which subst.exe
subst.exe is an external : C:\Windows\system32\subst.exe

Or even if you don't:
Code:
C:\BIN\JPSDK\LEStuff>which /a less
less is an alias : list
less is an external : D:\bin\util\less.exe

C:\BIN\JPSDK\LEStuff>which less.*
less.* is an external : D:\bin\util\less.*

C:\BIN\JPSDK\LEStuff>
 
Back
Top
[FOX] Ultimate Translator
Translate