Does this work with PowerShell?

[kiedtl]

Will this work with PowerShell on Linux/Windows Powershell?

Boost priority

• Boost priority in our backlog through Polar.sh. Higher pledge, higher priority.
• Minimum pledge by user/organization is $5, minimum amount for boost is $30.
• View all issues with pledges.
• We receive the funds once the issue is completed and confirmed by you.
• Features with the insiders label are released to sponsors first, and tied to a funding goal.

[pawamoy]

Not at all! But provided Powershell has ways of executing code before and after each interactive command, and disposes of a history which can be queried, it shouldn't be too hard to add support for it!

The shell code is only around 200 lines of code :slightly_smiling_face:

I'm gonna see what Powershell has to offer (or if you already have some knowledge about it, don't hesitate to share here!)

[pawamoy]

Question on StackOverflow: https://stackoverflow.com/questions/55972059/powershell-execute-things-before-and-or-after-an-interactive-command

• [ ] before
• [x] after: using prompt function

I don't know Powershell at all so if anyone could look into the suggestions made in the comments it would be great!

[kiedtl]

I'm not sure about the internals of shellhistory, but wouldn't it be possible to do with only an after function? Or would some features be broken?

[pawamoy]

It would not be broken, but the generated data could be inaccurate. If a command changes the working directory, or overrides itself or deletes itself (think of virtualenvs' deactivate function: it unsets itself at the end), then we could not compute its true type (file/function/alias etc).

We also need to get a timestamp before the command, to be able to compute its duration. That's actually the main reason for executing code before commands.

That said, maybe there are clever ways to do that in Powershell! Since it's a completely different shell, Bash/Zsh logic might not apply.