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've started working on correctly handling symlinked paths and have some questions about cwd implementation details.
Why does brush use its own Shell.working_dir instead of the system's std::env::set_current_dir/get_current_dir? It's because a subshell is not a new process?
The text was updated successfully, but these errors were encountered:
Yes, that's the main reason. It's been a source of friction along the way, but in practice, actual interactions with the filesystem have been relatively limited to I/O redirection, the source builtin, cd/pushd/popd, and a few other places.
If you look for everywhere the shell object can get cloned--and there's more places than would be ideal--you'll see where we leverage this.
reubeno
changed the title
corrent implementation of the physical -P and logical -L directories in cd, pwd and dirs
correct implementation of the physical -P and logical -L directories in cd, pwd and dirsOct 13, 2024
I've started working on correctly handling symlinked paths and have some questions about
cwd
implementation details.Shell.working_dir
instead of the system'sstd::env::set_current_dir/get_current_dir
? It's because a subshell is not a new process?The text was updated successfully, but these errors were encountered: