-
1. ### **Summary of the new feature / enhancement**
Currently, PowerShell does not notify the user that invoking a binary in `$PATH` which requires higher permissions (usually those of the superu…
-
When PowerShell is installed as a .NET global tool, it prepends its own `$PSHOME` folder to `$env:PATH`.
However, on macOS `$PSHOME` contains an _incompatible_ `pwsh` binary that is for _Linux_.
…
-
This makes the `ModuleIntrinsics.GetModulePath` function call add the directory `c:\users\\.nuget\packages\system.management.automation\6.1.1\runtimes\win-x64\lib\netstandard2.0\Modules` to the `$env:…
drocs updated
11 months ago
-
### Prerequisites
- [X] Write a descriptive title.
- [X] Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)
- [X] Search the ex…
-
### Prerequisites
- [X] I have written a descriptive issue title.
- [X] I have searched all [_open and closed_ issues](https://github.com/PowerShell/vscode-powershell/issues?q=is%3Aissue) to ensure i…
-
**Describe the bug**
I tried setting up `pwsh` as my shell in neovide, and then `:echo executable("pwsh")` is 0
**Expected behavior**
When I lanuch neovide from windows terminal, it can find …
-
## Steps to reproduce
Run the following with the latest preview version ([`7.1.0-rc.2`](https://github.com/PowerShell/PowerShell/releases/tag/v7.1.0-rc.2)) or the latest release version ([`7.1.0`](ht…
-
Need to remove the unneeded build artifact file `psoptions.json` from powershell windows packages.
Steps to reproduce
------------------
```powershell
dir $PSHOME\psoptions.json
```
Expect…
-
# Summary of the new feature/enhancement
As a scripter,
I want a `$PSUserHome` automatic variable that contains the path to the folder where a user profile, configuration file, etc. are stored,
s…
-
## Steps to reproduce
Launch PowerShell in your favorite terminal.
## Expected behavior
The prompt I've set up in my PowerShell profile.
## Actual behavior
I get the following boilerpla…