-
Notifications
You must be signed in to change notification settings - Fork 514
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
Postscript error on linux #44
Comments
I suspect this is due to the emoji font not being present. Let me push a fix real quick |
Should be fixed, or at the very least give a better error message. |
Let me know if you get the chance to confirm. Otherwise I will be closing this tomorrow |
I think that may be fixed. I'm getting a different error now:
|
Ah yup thats not very good is it... This msgbox library seems to be becoming less useful that I thought. Let me look into some alternatives. |
Do you have guifont set in your nvim init? |
I just pushed a change which should provide more useful panic messages on linux. |
I do have a font set with
|
Ok. I rewrote the font loading. Could you try again? I think it may be fixed. |
It works! I did get an error saying I had to enable DRI3 in my X11 GPU settings, but now it seems to work. Thanks for working to resolve this. Now I am able to open a window but I get a new error pretty frequently:
I also get a long scroll of |
Thats VERY strange. I'm not sure why it would be rendering out of window bounds. Can you hit me with a screen cap? |
Further setting RUST_BACKTRACE would be super useful so I can pinpoint where exactly the out of bounds error is happening (although I have a hunch) |
That's very interesting. Looks like you are using a window manager which is confusing winit (the window library). The error you are getting only happens when the window doesn't properly update neovim about the size of itself. Which is a very strange error. Can you give some details about your window manager and or try in a more standard window mode (I don't know if that's possible...). This feels a lot like an upstream issue... Sent with GitHawk |
There also seem to be some brutal perf shenanigans going on. Either that or the animating flag isn't getting set properly (this seems more likely) Sent with GitHawk |
I'm using i3. Pretty vanilla except some theming and some settings to deal with high DPI. I wouldn't be surprised if it's causing problems. Just about every app that isn't a terminal or web browser has visual bugs. I've never seen it cause a crash though. The animation choppiness was also there in reality about like in the recording. I can try on a different computer with some different window managers tomorrow. |
Sounds great. My current theory is dpi handling is wonky. Would you mind sharing your PC specs? I'm trying to zero in on what the performance problem is. I have a hunch that the animation isn't slow but is failing to finish the animation before going idle to save power Sent with GitHawk |
Yes, the out of bounds error doesn't happen in Gnome (a more standard desktop environment). But, when I try to j/k too far out of bounds it sometimes animates the cursor to the bottom-right of the window. My laptop is a Huawei Matebook Pro. Relatively new Intel i7 w/ integrated graphics. I still get the animation issues when switching to Nvidia MX150. I think you're right that it's just stopping/starting the animation incorrectly. When moving up/down lines the cursor often gets stuck half way or is a little too tall when it gets to the next line and doesn't reset till you move it again. Also one more bug: Clicking anywhere in the window (at least in Gnome) panics with this error:
|
Ok I rewrote the animation loop so I think it should be more stable. Could you make another issue with the mouse click error? That one seems super weird because I don't know how nvim_input_mouse could be an invalid method... |
thanks. will do |
When I try to run neovide on Ubuntu 19.10 I get the following error:
Failed to load by postscript name: NotFound
. Then it exits without opening any GUI window.Running with a stack trance gives this:
The text was updated successfully, but these errors were encountered: