-
Notifications
You must be signed in to change notification settings - Fork 249
[shell] respect ZDOTDIR for zsh startup files, and copy startup files instead of linking #1587
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
… instead of linking
I currently struggle to figure out if this is already released. Is it? 🙈 EDIT: I have the file |
Where can I see how Zsh is started with the |
Just using the EDIT: |
@weilbith it may help to file an issue so we have more info about your system, with the specific files so we can try to reproduce the problem, and can discuss there (rather than in the PR). I'm unable to repro your problem on my mac.
and then opening a |
You are right. Sorry for the noise. Will file in an issue with all details. |
Summary
Seeks to address two concerns that have arisen:
Zsh startup files are linked, not copied. We should copy. This was affecting a user who was mounting the filesystem which disallows linking in that scenario.
Fixes [Bug]: Fail to link .zshenv and .zprofile - invalid cross-device link #1536
ZDOTDIR was not respected for finding the ZSH startup files. We should support it as the zsh manual specifies that its the location of its startup files: https://zsh.sourceforge.io/Intro/intro_3.html
(Originally for [Bug]: zshenv is not sourced #1582 , but it seems that issue is unrelated to ZDOTDIR)
EDIT: Fixes #1582, as per user who reported the issue
How was it tested?
Tested by setting
ZDOTDIR=~/zsh-dot-dir
and moving my.zshenv
and.zshrc
files there. Starting adevbox shell
showed that these startup files were run.Moved them back to my homedir, and unset
ZDOTDIR
and starting adevbox shell
still worked as expected.