-
Notifications
You must be signed in to change notification settings - Fork 61
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
command line throwing errors #1
Comments
That looks horrible :( |
Hm, it looks like it's related indeed. Call me lazy, but it feels as if getting cygwin + zsh to run properly on multiple machines is not an easy task. |
same issue. |
As stated in the other issue thread, running |
nice, thanks. |
Hi, @yoshuawuyts , Did you fixed this issue by @iernie solution? I tried that solution, but it does not work. |
I use @twilek's solution which is in ohmyzsh/ohmyzsh#630 fixed this issue. |
@earthday great you solved it! I ditched zsh because installing it between all my machines caused way too many issues, despite it being a great CLI. |
I haven't had any issues with zsh after this one. Use it at work every day and works great now. |
I have this same problem, but in my Cygwin64 installed and not any of the solutions works. Not 'rm -f ~/.zcompdump; compinit' or 'compaudit | xargs chmod g-w' |
@juantm Try method I mentioned. In my PC, I use cygwin x86 version on Win8. There are two files in cygwin home folder, one is ".zcompdump", another is ".zcompdump-BrightChen-PC-5.0.2". Copy the first file's content into the second one. This solution fixed my problem. cp ~/.zcompdump ~/.zcompdump-BrightChen-PC-5.0.2 |
Thanks, I finally resolved the problem with just running 'zsh -l' without Juan Toro Marty 2013/12/22 Bright Chen notifications@github.com
|
Had the same issue here: Cygwin + Oh-my-zsh on Win 8.1 x64. @twilek's solution worked like a charm. |
I have the same issue: Cygwin x86 + oh-my-zsh on Windows 7 x64. |
thank you @earthday your solution fixed the issue for me!! |
thanks @earthday , it works. |
Nothing that really hampers my workflow, but every time I start the command line it spews up the following:
Any idea as to what may cause this?
The text was updated successfully, but these errors were encountered: