You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe I'm using the suggested way of adding entries to my PATH as described at the bottom of env.nu but those entries are added relative to whatever directory I opened the nushell in, rather than relative to my home directory.
Nesting nushells results in appended PATH entries i.e. if your outer nushell was started in your home directory, you cd somewhere else and start another nushell, that one will have the incorrect PATH entries in addition to the correct ones from the first shell.
How to reproduce
Add a line like let-env PATH = ($env.PATH | split row (char esep) | prepend '.local/bin') to your env.nu
A:
Open a terminal with a non-nu-shell
cd anywhere besides ~/
start nushell
B:
run nushell in zellij
cd anywhere besides ~/
open a new pane or tab
Expected behavior
My PATH is identical to if I had started a terminal with nushell in my home directory.
Screenshots
No response
Configuration
key
value
version
0.81.0
branch
commit_hash
build_os
linux-x86_64
build_target
x86_64-unknown-linux-gnu
rust_version
rustc 1.69.0 (84c898d65 2023-04-16)
rust_channel
stable-x86_64-unknown-linux-gnu
cargo_version
cargo 1.69.0 (6e9a83356 2023-04-12)
build_time
2023-06-07 13:38:04 +02:00
build_rust_channel
release
features
default, sqlite, trash, which, zip
installed_plugins
Additional context
No response
The text was updated successfully, but these errors were encountered:
I've tried to reproduce this on my mac and couldn't. However, I did find that launching nu from within nu creates duplicate entries, even though I have a line in my config.nu to remove duplicate path entries.
Describe the bug
I believe I'm using the suggested way of adding entries to my PATH as described at the bottom of
env.nu
but those entries are added relative to whatever directory I opened the nushell in, rather than relative to my home directory.Nesting nushells results in appended PATH entries i.e. if your outer nushell was started in your home directory, you cd somewhere else and start another nushell, that one will have the incorrect PATH entries in addition to the correct ones from the first shell.
How to reproduce
let-env PATH = ($env.PATH | split row (char esep) | prepend '.local/bin')
to your env.nuA:
B:
Expected behavior
My PATH is identical to if I had started a terminal with nushell in my home directory.
Screenshots
No response
Configuration
Additional context
No response
The text was updated successfully, but these errors were encountered: