We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
when i run mancy from terminal on macOs ,the following is output:
➜ ~ mancy ➜ ~ [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0 [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0 [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0 [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0 [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
Mancy starts and everything works as expected. However, your command history is not persisted and the terminal remains stuck.
The issue can be fixed by using the fix as per spyder-ide/spyder#3730 (comment)
export EVENT_NOKQUEUE=1
However, it would be great if this just worked as is. I had installed Mancy using npm -g
npm -g
The text was updated successfully, but these errors were encountered:
No branches or pull requests
when i run mancy from terminal on macOs ,the following is output:
➜ ~ mancy
➜ ~ [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
Mancy starts and everything works as expected.
However, your command history is not persisted and the terminal remains stuck.
The issue can be fixed by using the fix as per spyder-ide/spyder#3730 (comment)
export EVENT_NOKQUEUE=1
However, it would be great if this just worked as is.
I had installed Mancy using
npm -g
The text was updated successfully, but these errors were encountered: