-
Notifications
You must be signed in to change notification settings - Fork 21
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
The latest version 1.0 & 1.0.1 install failed #39
Comments
Hi @JohnWickzzz, can you provide the following information:
|
sorry, forgot to say. |
Have you installed codesnap another version before? Since v1.0.0 codesnap has break change, can you try clean codesnap plugin use Lazy, and reinstall it again? |
I tried to uninstall and reinstall several times, but I get the same error every time. |
Thx for your bug report, I'll check as soon |
Hi @JohnWickzzz can you try again with codesnap.nvim the latest version? |
Sorry, the error still occurred when I intall the latest version. Failed to source vim/_editor.lua:0: /Users/lee/.config/nvim/init.lua..nvim_exec2() called at /Users/lee/.config/nvim/init.lua:0../Users/lee/.local/share/nvim/site/lazy/codesnap.nvim/plugin/codesnap.lua: Vim(source):E5113: Err stacktrace:
|
Mac arm arch & Linux x86_64 works fine, I'll check it again |
Although an error occurred during installation, when I use the command CodeSnap, it successfully generated snapshot and copied. |
Before refactor, the snapshot is generated by browser, which means whenever you start an Neovim instance, there will be a WS server running in background to receive messages from the Neovim instance and send messages to the browser. And the browser will parse DOM tree and create a snapshot then copy it into your clipboard, live preview is cool and browser can render beautiful pictures easier than lower graphic API, but it may bring additional performance overhead, and you still need to use your mouse to click the copy button to trigger snapshot action. After refactor, the snapshot is generated by skia engine(the tiny implementation), and communicate with Neovim via FFI, the snapshot image is just created without starting any web server and browser, this solution will perform better and you don't have to click anything use mouse to take a snapshot (most Neovim user hate that). The new solution is experimental, I like the live-preview page, and I also like take snapshot just one command, perhaps we can find better solution in the future. And thx for using codesnap.nvim, I'm glad to hear that someone says like some feature of codesnap.nvim :) |
I'm using Arch Linux, and Neovim v0.95. The latest version of codesnap still not working. The same problem with @JohnWickzzz. But I can't generate the snapshot. |
@jenkinpan what is arch of your Arch Linux? |
I run codesnap.nvim works fine on my x86_64 Arch Linux, I have updated document, did u forget add { "mistricky/codesnap.nvim", build = "make", version = "^1" }, |
I'm also use arch linux, and I add make in it, the config is right. I try to reinstall it after I clean it by using Lazy. but it also remind me there are some mistakes. |
I got the same issue, running Fedora 39 with nvim version:
and with the following plugin config (with lazy.nvim):
I get an error message during the initial installation. After restarting nvim, i can run Interestingly, the error i see during the installation contains the following line:
Looks like there is something wrong with the generator library. Is there a way to rebuild that locally? |
|
Looks like v0.0.1 is not ready for release now, I'll revert codesnap.nvim to 0.0.11 |
If anyone has been upgrade codesnap.nvim to v1.0.x, clear cache and reinstall codesnap.nvim will install v0.0.11, and it should be works fine |
This issue is described in v1.0.x, but the version has rolled back to v0.0.11, so closed now. |
CodeSnap v1.0.0 was released, If there are any issues I will reopen this issue |
@mrWinston The readme was updated, you can follow the latest version of the docs to build codesnap.nvim manually |
😁 I decide to stay at 0.0.11 version, cause I prefer the CodeSnapPreviewOn command. Thanks for your work! |
Failed to source
/Users/lee/.local/share/nvim/site/lazy/codesnap.nvim/plugin/codesnap.lua
vim/_editor.lua:0: /Users/lee/.config/nvim/init.lua..nvim_exec2() called at /Users/lee/.config/nvim/init.lua:0../Users/lee/.local/share/nvim/site/lazy/codesnap.nvim/plugin/codesnap.lua: Vim(source):E5113: Err
or while calling lua chunk: vim/loader.lua:0: dlopen(/Users/lee/.local/share/nvim/site/lazy/codesnap.nvim/lua/generator.so, 0x0006): tried: '/Users/lee/.local/share/nvim/site/lazy/codesnap.nvim/lua/generator.s
o' (mach-o file, but is an incompatible architecture (have (arm64), need (x86_64h)))
stack traceback:
^I[C]: in function 'error'
^Ivim/loader.lua: in function <vim/loader.lua:0>
^I[C]: in function 'require'
^I...share/nvim/site/lazy/codesnap.nvim/lua/codesnap/init.lua:3: in main chunk
^I[C]: in function 'require'
^I...l/share/nvim/site/lazy/codesnap.nvim/plugin/codesnap.lua:1: in main chunk
^I[C]: in function 'nvim_exec2'
^Ivim/_editor.lua: in function 'cmd'
^I.../share/nvim/site/lazy/lazy.nvim/lua/lazy/core/loader.lua:485: in function <.../share/nvim/site/lazy/lazy.nvim/lua/lazy/core/loader.lua:484>
^I[C]: in function 'xpcall'
^I...al/share/nvim/site/lazy/lazy.nvim/lua/lazy/core/util.lua:113: in function 'try'
^I...
^I.../share/nvim/site/lazy/lazy.nvim/lua/lazy/core/loader.lua:191: in function 'load'
^I.../share/nvim/site/lazy/lazy.nvim/lua/lazy/core/loader.lua:123: in function 'startup'
^I.../.local/share/nvim/site/lazy/lazy.nvim/lua/lazy/init.lua:110: in function 'setup'
^I/Users/lee/.config/nvim/lua/core/pack.lua:135: in function 'load_lazy'
^I/Users/lee/.config/nvim/lua/core/pack.lua:138: in main chunk
^I[C]: in function 'require'
^I/Users/lee/.config/nvim/lua/core/init.lua:160: in function 'load_core'
^I/Users/lee/.config/nvim/lua/core/init.lua:170: in main chunk
^I[C]: in function 'require'
^I/Users/lee/.config/nvim/init.lua:2: in main chunk
stacktrace:
The error msg.
The text was updated successfully, but these errors were encountered: