2 ms·
Same for me. Windows PowerShell now conveniently comes with PSReadLine, that enables to just hit on CTRL+R, write some keywords (and maybe after few more CTRL+R
by jve 5y ago
Same for me. Windows PowerShell now conveniently comes with PSReadLine, that enables to just hit on CTRL+R, write some keywords (and maybe after few more CTRL+R hits), and that historical command pops out whenever I need it.
Even better, newer versions support predictions [0] - which, whenever you type any text, it immediately lists multiple commands where it finds a match.
Of course, that addresses only myself, but not whoever touches the project. As well, I may not know in what context that command was ran. So I appreciate some suggestions here that guide toward making scripts and providing useful info in README.
[0] https://youtu.be/VT2L1SXFq9U?t=2594 https://youtu.be/VT2L1SXFq9U?t=2594
- majkinetor 5y agoUse Invoke-Build as portal to other scripts in the repo. Document scripts using README.md in their own folder. Then users of your project can type `ib ?` to get the list of available scripts and ib itself will setup context of their execution as needed.