3 ms·
How well does it handle differences between various shells and their common tools? Since it's called "explain /shell/", I just had to try inputting some basic
by mdisraeli 13y ago
How well does it handle differences between various shells and their common tools?
Since it's called "explain /shell/", I just had to try inputting some basic powershell as a test - Sadly it's not supported yet :P
- ygra 13y agoAt least for PowerShell such a thing should be trivial as the shell knows about its commands and parameter parsing is consistent for every command. I'll probably try hacking something together on the weekend for PS.
- mdisraeli 13y agoAwesome, thank you! :D
- ygra 13y agoNot progressing as fast as I'd like. Stumbled over a few roadblocks regarding parameter binding. The rules are complex (and underdocumented, I might add. E.g. why man gci displays three parameter sets, or why -fi always binds to -filter and not to -file is unknown to me. CmdletInfo.ResolveParameter sounds like being great in theory but is unusable in practice. At least when I'm done I might be able to revisit parameter binding in Pash. Preliminary repo is at https://github.com/ygra/ExplainPS https://github.com/ygra/ExplainPS – once parameter binding is done the rest is just fetching information from Get-Help which is the actual trivial part.