Jay comments

Results 50 comments of

Jay

Coexistence of posh-git and miniconda. Can't suppress warning: "If your prompt function uses any posh-git commands, it will cause posh-git to be re-imported every time your prompt function is invoked."

Adding an update. I took a dive into the `posh-git` internals and identified that the warning is coming from this code-block in [posh-git.psm1](https://github.com/dahlbyk/posh-git/blob/bbc5ac380018239e0ac70411a59f4e367ca87f2d/src/posh-git.psm1#L147): ```powershell # Install handler for removal/unload of...

Coexistence of posh-git and miniconda. Can't suppress warning: "If your prompt function uses any posh-git commands, it will cause posh-git to be re-imported every time your prompt function is invoked."

## SOLUTION I "solved" my issue with the following steps: 1. Commented out the [Write-Warning line](https://github.com/dahlbyk/posh-git/blob/bbc5ac380018239e0ac70411a59f4e367ca87f2d/src/posh-git.psm1#L159) from [posh-git.psm1](https://github.com/dahlbyk/posh-git/blob/bbc5ac380018239e0ac70411a59f4e367ca87f2d/src/posh-git.psm1#L147). 2. Enabled the `PSFeedbackProvider` "Experimental Feature" with `Enable-ExperimentalFeature -Name PSFeedbackProvider`. This suppresses...

Coexistence of posh-git and miniconda. Can't suppress warning: "If your prompt function uses any posh-git commands, it will cause posh-git to be re-imported every time your prompt function is invoked."

Yet another bit of info to add. The `Suggestion [4,General]: The most similar commands are:` output will always appear whenever the `$Error` variable is populated and the PSFeedbackProvider experimental feature...

Coexistence of posh-git and miniconda. Can't suppress warning: "If your prompt function uses any posh-git commands, it will cause posh-git to be re-imported every time your prompt function is invoked."

Hmm, that doesn't seem to be working for me. Example code: ```powershell $OutputEncoding = [console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new() Import-Module posh-git -Force -ErrorAction 0 | Out-Null $GitPromptSettings.DefaultPromptPrefix.Text = '$(Get-Date -f...

Coexistence of posh-git and miniconda. Can't suppress warning: "If your prompt function uses any posh-git commands, it will cause posh-git to be re-imported every time your prompt function is invoked."

More troubleshooting... ```powershell function DisableConda { if($env:CONDA_IS_ENABLED -eq $true){ Remove-Module -FullyQualifiedName "$Env:_CONDA_ROOT\shell\condabin\Conda.psm1" -ErrorAction Ignore | Out-Null $env:CONDA_IS_ENABLED = $false } } ``` Simply unloading the Conda.psm1 file causes all this:...

Coexistence of posh-git and miniconda. Can't suppress warning: "If your prompt function uses any posh-git commands, it will cause posh-git to be re-imported every time your prompt function is invoked."

> Try adding something like this before the `Set-Item`? > > [posh-git/src/posh-git.psm1](https://github.com/dahlbyk/posh-git/blob/bbc5ac380018239e0ac70411a59f4e367ca87f2d/src/posh-git.psm1#L136-L137) > > Lines 136 to 137 in [bbc5ac3](/dahlbyk/posh-git/commit/bbc5ac380018239e0ac70411a59f4e367ca87f2d) > HACK: If prompt is missing, create a global one...

Coexistence of posh-git and miniconda. Can't suppress warning: "If your prompt function uses any posh-git commands, it will cause posh-git to be re-imported every time your prompt function is invoked."

> Or another option would be to try patching posh-git's `OnRemove` to avoid the warning. I would guess removing miniconda removes `prompt` altogether, which we can probably detect to suppress...

[BUG] ERR_INVALID_URL when running "merge-markdown -m .\manifest.yml" on Windows 10.

I don't mean to be demanding, but could you possibly include the functionalty to process absolute paths? I appreciate the help!

Can we supress the new experimental warning from the new default require(esm) setting?

> You can use [`node --no-deprecation`](https://nodejs.org/docs/latest/api/cli.html#--no-deprecation) or `export NODE_OPTIONS="--no-deprecation"`. How can I do this globally though? `export NODE_OPTIONS="--no-deprecation"` in console just gives me ``` export: The term 'export' is not...

Can we supress the new experimental warning from the new default require(esm) setting?

I also created a machine-wide environment variable called `NODE_OPTIONS` and set its value to `--no-deprecation`. I'm still getting the ExperimentalWarning. It's even happening when I run `npm list -g --depth=0`....