-
-
Notifications
You must be signed in to change notification settings - Fork 25.7k
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
Oh my zsh update broke sshfs folder #8541
Comments
Can you post your zshrc file? |
All other lines are commented out. |
Not sure if you have the same issue, but I had this as well. In my situation, Im running debian 10, kernel 4.19.0-6 The error I was getting was that the /root/ssh/authorized_keys file could not be found, but as we all know that is NOT the correct path. It should be /root/.ssh/authorized_keys Im not sure how or why this changed, but to confirm the validity, I ran mv .ssh ssh and everything started working again. Im thinking of setting up tripwire on a clean image and installing ohmyzsh again to see how this got changed. |
It does not resolve the underlying issue with ohmyzsh. |
Does |
I think I have found the origin of the problem, so I'm posting here. For some reason, when you do a git command on a sshfs directory, it takes forever, so is more of a GIT -> sshfs problem than zsh or ohmyszh. Since ohmyszh automatically git status and some other commands for git directories, if you have this setup like mine, this is the problem, there's any config to ohmyszh avoid read GIT info on certain directories? |
There is a way to do, but we will have to run it in each subdirectory:
Ideally, I want to do it for all subdirectories. |
So this is just |
Yes that is exactly what it happens. For now I'm just. not using it because
i have to use a SSHFS drive all day, just thought to give you a warning,
thanks for the response.
atenciosamente,
Marco Aurélio Simão
…On Sat, Jan 2, 2021 at 6:37 PM Marc Cornellà ***@***.***> wrote:
So this is just git breaking in sshfs directories, if I understand
correctly? If that is the case, this should be fixed by async-ing the git
calls in git prompts (work in progress).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8541 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASTOEWUEGDDNQU4E2M643LSX6GYLANCNFSM4KHFR6TA>
.
|
Hi, |
I am also experiencing the same issue. Thank you for your work. Please fix. :) |
I think it is.
…On Thu, Apr 15, 2021, 00:55 Jon Watson ***@***.***> wrote:
I am also experiencing the same issue. Thank you for your work. Please
fix. :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8541 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASTOES2OP56FCUT5LHXFKTTIZPSPANCNFSM4KHFR6TA>
.
|
I am using macOS Catalina.
Everything worked fine until the latest update.
zsh version: zsh 5.7.1 (x86_64-apple-darwin19.0.0)
Everything looks okay for normal folder. However, for remote file systems, it is stuck, until I press Ctrl +C and then type
cd ..
I am attaching the screenshot below:
The text was updated successfully, but these errors were encountered: