Replies: 1 comment
-
Thank you very much for your feedback. I totally agree with you. I will take more care with 2.9.8 on customization on .zshrc and .bashrc, kitty and neovim. Do you see more critical configurations that should be protected by default after the initial installation? And another question. Where do you save your local customization. In the Dotfiles folder (with symlinks) or .config? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Some of us have our own world view of how we want our terminal to be. Every time I upgrade, I get forced into a posh environment, which I never asked for, and don't like using. The only thing I don't like about all this work you've done is this issue about .zshrc. I've tried forcing the upgrade to keep my version of .zshrc, but it doesn't work. Every time, I must go in and copy my saved copy of .zshrc over my original that you've written over. Man, don't mess with people's .zshrc or .bashrc files. Some of us really spend a lot of time in the terminal, and we have it like we want it. I haven't taken the time to dig into your code to figure out why my .zshrc is getting overwritten every time, but I'd appreciate you looking into it, and perhaps imagining that some of us need that little snippet of code to work properly. You have code in your .zshrc that will source any .zshrc_custom that we users may want to implement, but that doesn't work if our .zshrc_custom is trying to implement a different oh-my-zshrc theme and settings after you've already sourced posh and all your aliases and other things. posh is already sourced, and our customizations don't initialize.
Beta Was this translation helpful? Give feedback.
All reactions