hard to tell what's wrong in case of root installed zsh #200
Comments
|
Did you manage to solve it? |
|
@HagaiHargil No, I didn't tackle it yet. I'm on a big new change introducing multi-panels and completion (in the "panels" branch) and everything else is frozen until I've finished it. I've noted the interest in the issue, which matters a lot when I prioritize tasks. |
|
@Canop I completely understand, thanks for taking the time to do such a large and important refactor! I'm sorry if my message was hinting otherwise, I was simply trying to understand whether there's a "manual" fix I can try, since your initial report suggested that you are aware of a way to overcome it. |
|
There's absolutely no problem in asking, no worry. I don't think there's a hard problem here, other than finding the time to do a not terribly exciting change, and a rather painful one when it comes to thoroughly testing all paths. |
|
I just wanted to document that if I simply run |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

This probably applies to other cases.
What was observed for a user having zsh non used and installed as root was this:
and the log contained
The problem was the non accessible .zshrc.
This should be easier to diagnostic and should not block the whole installation.
The text was updated successfully, but these errors were encountered: