-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Nothing rendered in the preview pane #3
Comments
Hi, could you tell me, which packages of vim and/or neovim you have installed, and how is configure your vim and gvim alternative? ~$ update-alternatives --display vim
~$ update-alternatives --display gvim The problem is with vim backend, which is start on background as server, but I don't know why. |
Hi, I really like formiko-vim! Should I hijack this thread because the title is accurate? If not I can repeat the post into another issue, here it goes: I recently started using nvidia drivers, now can't get any preview.
And I'm using debian bullseye (clean install a few days ago after the drivers mess, except that they are I hope this is not a painful bug
|
Hi, thanks, but this is different error, and it looks to OpenGL problem with your driver. Can you sand me your source code? Did you try generate same specific HTML? Or including specific image, video or something like that? I can handle this error, if i can replicate it. |
Hi! I tried many files from I did got good renders before installing the nvidia drivers though... So I tried removing and reinstalling ( I'm using debian 11 on an old MacBook Pro 5,2 (late 2010 so without nvidia drivers gnome looks laggy af).
Maybe
Thanks! |
Using formiko v1.3.0 as packaged on Ubuntu 18.04, I get nothing rendered in the preview pane.
Have followed the instructions in the README.md of this repo and that hasn't helped.
Running formiko-vim from the CLI there are a couple of errors displayed.
FWIW - I'm using neovim, but I doubt this is an issue as the editor pane is working just fine with the embedded vim instance.
The text was updated successfully, but these errors were encountered: