- Jun
- 59
- 0
Any chance of making it user customizable? For example, I have the following alias
alias cd=call c:\cmd\cd.btm
so quick help displays call c:\cmd\cd.btm --- not very helpful.
An easy way of doing the customization would be to check for another alias of the form qh_alias-name and display its value if present. Then I could
alias qh_cd=`cd [ /P | /A ] [ /N ] [ /? | /H ] [ ~ | - | ? | path ]`
to get some useful help. Would be nice---I always forget that I implemented the ? special character for the path (uses @getfolder to get a directory to cd to).
Obviously one can come up with other mechanisms to associate the custom help. For example, a command aliashelp alias=help-text; but this would need an internal table of help texts and a /R style load mechanism.
My suggestion above probably requires the least amount of modification to TCC. In addtion, this could also work for anything, not just aliases. You could check for the alias qh_name where name would be the cmd/btm/bat/exe/executable-extension/etc name with extension but without path.
alias cd=call c:\cmd\cd.btm
so quick help displays call c:\cmd\cd.btm --- not very helpful.
An easy way of doing the customization would be to check for another alias of the form qh_alias-name and display its value if present. Then I could
alias qh_cd=`cd [ /P | /A ] [ /N ] [ /? | /H ] [ ~ | - | ? | path ]`
to get some useful help. Would be nice---I always forget that I implemented the ? special character for the path (uses @getfolder to get a directory to cd to).
Obviously one can come up with other mechanisms to associate the custom help. For example, a command aliashelp alias=help-text; but this would need an internal table of help texts and a /R style load mechanism.
My suggestion above probably requires the least amount of modification to TCC. In addtion, this could also work for anything, not just aliases. You could check for the alias qh_name where name would be the cmd/btm/bat/exe/executable-extension/etc name with extension but without path.