takekazuomi / posh-direnv Goto Github PK

The version of posh-direnv on PSgallery does not appear correct. Specifically the posh-direnv.psm1 file

Hi,

Can we please get the same approval and apply commands exposed for reuse via the command line?

As a power user, I want to manage the .psenvrc content myself, without having to launch notepad every time.

Hi,

posh-direnv often silently fails to apply .psenvrc changes. I go through the Edit-DirEnvRc workflow, and even close and relaunch PowerShell. But still, the changes fail to take effect.

As a workaround, I have to repeat the same Edit-DirEnvRc steps over and over. Sometimes I add a dummy blank line, save, then delete the line, resave, and quit notepad.

I suspect the root cause has to do with posh-direnv's overly aggressive requirement for the file contents to be detected to change. In other words, we can improve posh-direnv accuracy by dropping the code that performs difference checks. Just always approve and apply the latest .psenvrc contents on disk, when notepad exits without an error status code.

Update

Even with NO changes to the .psenvrc file, posh-direnv often fails to load the configuration into the PowerShell environment. I very often have to manually execute Edit-DirEnvRc, add a blank line, save, delete the blank line, save, and quit notepad. In order for the existing .psenvrc contents take effect.

Microsoft has changed the default PowerShell policy. The following requirements are now in effect:

• The execution policy must be opened up to at least RemoteSigned level, especially for typical desktop/laptop Windows envionments.
• Execution policy changes must be done in an elevated PowerShell context.
• PowerShell module installation must be done in an elevated PowerShell context.

Example:

1. Launch PowerShell in administrative mode.
2. Run Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
3. Run Install-Module -Name posh-direnv

Reference:

https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.1

Could we update the README to reflect more of these relevant installation details?

Use GitHub Action to push to powershell gallery at the time of release.

https://docs.github.com/en/actions/reference/events-that-trigger-workflows#release

You will need to add some automated testing.

Any reason why posh-direnv should not work on win2019 server?