-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
Unclutter $HOME
#200
Comments
Given that the target audience of the kit is new ZSH users, to avoid confusion I think that the kit should keep using All that said, I think it'd be a good idea to honor
I'm pretty busy for the next couple of weeks, but I'd definitely be willing to merge a PR that implemented it in a backwards-compatible fashion - not breaking existing users is high priority when making changes to the kit. |
Feature Request
Is your feature request related to a problem? Please describe
The kit, together with
zsh
, intstalls/requires quite a lot stuff at$HOME
:Dirs:
zgenom
,zsh-quickstart-kit
,.fzf
,.zgenom
,.zqs-settings
,.zsh
,.zshrc.d
,.zshrc.pre-plugins.d
.Files:
.fzf.zsh
,.p10k.zsh
, several.zcompdump*
files,.zsh-history
,.zsh-quickstart-last-update
,.zsh-quickstart-local-plugins
.Symlinks:
.zgen-setup
,.zsh_aliases
,.zsh_functions
,.zshrc
.Describe the solution you'd like
Unclutter
$HOME
by following XDG dir specification where possible.Describe alternatives you've considered
Moving and symlinking stuff by hand, but that's obviously tedious and probably incompatible with auto-update. Symlinks would still clutter
$HOME
.Additional context
zsh
files paths (.zshrc
,.zcompdump*
, etc.) are semi-hardcoded by default, but can be put in more appropriate paths, as explained on ArchWiki. Which means that zqs install script should account for the possibility of altered paths and, ideally, allow user to alter them post-install without breaking the kit.The text was updated successfully, but these errors were encountered: