Skip to content
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

Cannot use Quarto commands #76

Closed
carrascomj opened this issue Jul 5, 2023 · 4 comments · Fixed by #77
Closed

Cannot use Quarto commands #76

carrascomj opened this issue Jul 5, 2023 · 4 comments · Fixed by #77

Comments

@carrascomj
Copy link

carrascomj commented Jul 5, 2023

When I run :QuartoPreview, I get this:

E5108: Error executing lua ...g/.local/share/nvim/lazy/quarto-nvim/lua/quarto/init.lua:47: at
tempt to index field 'uv' (a nil value)                                                      
stack traceback:                                                                             
        ...g/.local/share/nvim/lazy/quarto-nvim/lua/quarto/init.lua:47: in function 'quartoPr
eview'                                                                                       
        [string ":lua"]:1: in main chunk

I am using the config jmbuhr/quarto-nvim-kickstarter@dce6da4 as is (latest commit). It did not work with the previous commit or by installing quarto.nvim with its dependencies on my own config.

Nvim version:

NVIM v0.9.1
Build type: Release
LuaJIT 2.1.0-beta3
@carrascomj
Copy link
Author

carrascomj commented Jul 5, 2023

Found the culprit: vim.uv was deprecated in favor of vim.loop.

Maybe the version should be tied to 0.9.0 instead of >=0.9.0.

@jmbuhr
Copy link
Collaborator

jmbuhr commented Jul 5, 2023

The deprecation is the other way around. But I stick with loop until nvim 0.10 is the stable version, just updated too soon.

@jmbuhr jmbuhr closed this as completed in aa42597 Jul 5, 2023
@carrascomj
Copy link
Author

You are completely right, I read it wrong. Changing uv for loop works on 0.9.1, for the most part.

@jmbuhr
Copy link
Collaborator

jmbuhr commented Jul 5, 2023

latest release has the fix now, thanks for the catch!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants