Title: Re: Zsh Broke init.sh Again
Hi James, Max, Kevin, et al,
I think James is right on track. It’s clear from his statement about error messages depending on shell options that he’s tested this in ways I haven’t. I do believe that there are lots of zsh users and given it’s immense power and huge set of features, the number will doubtless grow. With the options that I and my friends use (many use my init scripts) there are no error messages. Problems occur only when the script is sourced multiple times, which results in multiple entries in the path. Inexperienced users wouldn’t even notice that symptom.
I agree with avoiding a separate init.zsh script. James’ script is spectacular evidence of the power of zsh. For instance, instead of multiple tests and separate function that use indirect references, path updates in James’ script are single assignment statements. I’ve saved it and plan to incorporate many of it’s great ideas in my own init scripts. However, this elegance and the need for a separate script complicate maintenance. My latest fix is far more robust than my last and I don’t believe that changes in zsh will break it again. Thus, I would have to vote for simplicity of maintenance in this case. However, it might not be a bad idea to include James’ script with Fink anyway. You wouldn’t even have to document it. Clever users would find it anyway and appreciate it as a wonderful example even if they didn’t use it!
--
Gary
~~~~
Computer guru, n.
A user that actually reads the manual.
