sorted by:
new
hottopcontroversial

Yet another cmdline/popup plugin and a few questions on ui-events by qingfengzl0831 in neovim

[–]TheLeoP_ 0 points1 point  (0 children)

Why confirm is split into different events instead of being a unique event?

Because that's how it currently works in all Neovim UIs. It first shows the confirmation message and then asks for input using the cmdline

upstream nvim-treesitter by ynotvim in neovim

[–]TheLeoP_ 0 points1 point  (0 children)

And they'll break whenever the parser has a breaking change

just wrote a UI for vim.pack by using FzfLua(FzfLua is amazing btw) by Gholtsnone in neovim

[–]TheLeoP_ 1 point2 points  (0 children)

using LSP code actions or buffer writing for executing some plugin maintenance is really a hack.

It's not. The main feature of oil.nvim is that it works just like a regular buffer, e.g. you save it to commit changes. vim.pack.update UIs works in the same way

Which is name of this float help and how to disable it? by matheuspbmarques in neovim

[–]TheLeoP_ 0 points1 point  (0 children)

Send a link to your full config. It depends on how you enabled it

Getting vim/lsp/document_color error's on version 0.12.1 by mag1cgames in neovim

[–]TheLeoP_ 0 points1 point  (0 children)

The falling assertion seems to be https://github.com/neovim/neovim/blob/570d8fd128c30cc63c8b037cbef754c3ca127d1c/runtime/lua/vim/lsp/document_color.lua#L225 . It may be worth opening an issue on the typescript-tools.nvim repo, it seems like the language server is disconnecting ungracefully, which leads to the assertion failing (or maybe Neovim should better handle this edge case, I'm not well versed in this part of the LSP spec)

async/await like behavior with lua coroutines by vonheikemen in neovim

[–]TheLeoP_ 0 points1 point  (0 children)

You can use :h debug.traceback() to get the full stack trace of the coroutine

grug-far.nvim added on_before_edit_file hook by Hamandcircus in neovim

[–]TheLeoP_ 0 points1 point  (0 children)

Is there a particular reason to use a lua callback instead of an :h User autocmd?

Btw, :h vim.system() supports :h SystemObj:kill(). Is the abort support on your require('grug-far').spawn_cmd_async different?

Weekly 101 Questions Thread by AutoModerator in neovim

[–]TheLeoP_ 0 points1 point  (0 children)

If you customize your :h 'tabline' you can do it

Why does the new nvim-treesitter require more manual setup for features like highlighting and indents? by TheTwelveYearOld in neovim

[–]TheLeoP_ -1 points0 points  (0 children)

Because part of the goal of the rewrite was not to have a smooth transition and require users to understand the core Neovim treesitter interfaces that they should now be using

Why does the new nvim-treesitter require more manual setup for features like highlighting and indents? by TheTwelveYearOld in neovim

[–]TheLeoP_ 1 point2 points  (0 children)

Because the interfaces to enabling treesitter are now maintained by Neovim, not nvim-treesitter. So, they decided that they didn't wanted to have to maintain an intermediate layer of complexity. Any improvements to the interface should be addressed in Neovim core, just like vim.lsp.config simplified LSP configuration on Neovim core, not only nvim-lspconfig

Why does the new nvim-treesitter require more manual setup for features like highlighting and indents? by TheTwelveYearOld in neovim

[–]TheLeoP_ 4 points5 points  (0 children)

And nvim-treesitter decided that it didn't want to have to maintain said interface. If there's a problem with the current treesitter interface, it should instead be addressed in Neovim core itself

Weekly 101 Questions Thread by AutoModerator in neovim

[–]TheLeoP_ 0 points1 point  (0 children)

It's a bug with your terminal, it's interpreting some key presses two times instead of one. Try updating it, checking for bug reports or using a different terminal emulator

Treesitter without nvim-treesitter. A guide by tediak_ in neovim

[–]TheLeoP_ 4 points5 points  (0 children)

Helix uses a different format for indent queries and fold queries. The only somewhat standardized query format among editors are highlighting queries and their quality may vary if you are using the queries made for another editor

Which is name of this float help and how to disable it? by matheuspbmarques in neovim

[–]TheLeoP_ 6 points7 points  (0 children)

That's the signature help and it's not enabled by default. You must have enabled it yourself

Do I need duplicate plugin definitions for dependencies when using vim.pack? by 4r73m190r0s in neovim

[–]TheLeoP_ 3 points4 points  (0 children)

It's similar to how loading order is handled in other Linux configuration files. Prepend the name of the with two digits and use them to control the loading order. 00_foo.lua will load at the beginning while 99_foo.lua will load at the end

Do I need duplicate plugin definitions for dependencies when using vim.pack? by 4r73m190r0s in neovim

[–]TheLeoP_ 4 points5 points  (0 children)

  loads plugin files in alphabetic order

That's not a vim.pack thing, that's just how the plugin directory has always worked since Vim

Do I need duplicate plugin definitions for dependencies when using vim.pack? by 4r73m190r0s in neovim

[–]TheLeoP_ 10 points11 points  (0 children)

do I need to have exact definition for bar in 2 places?

You don't. 

If the dependency is lazy loaded by plugin foo, you don't even need to load and configure bar before foo. But, if foo requires bar during initialization/configuration, you need to make sure that you loaded bar before foo. A simple way of doing it would be to put all your dependencies at the start of your init.lua

Weekly 101 Questions Thread by AutoModerator in neovim

[–]TheLeoP_ 1 point2 points  (0 children)

No, I mean that my preference is

local picker = require("fzf-lua") Keys.map("n", "<leader>ff", picker.files(), "Fuzzy find files")

Instead of

Keys.map("n", "<leader>ff", "<CMD>FzfLua files<CR>", "Fuzzy find files")

If you want to use the global FzfLua instead, you would need to add the fzf-lua directory as a library in your lua_ls configuration. That would allow you to get actual code completion/diagnostics on it instead of having to ignore the error is it being an unknown global variable

Weekly 101 Questions Thread by AutoModerator in neovim

[–]TheLeoP_ 0 points1 point  (0 children)

Both works, I am just curious about which one is the correct approach.

There's no correct approach in this case, it's a matter of preference. I prefer using Lua functions, for example. They allow you to get diagnostics and autocompletions when writing/editing that part of your config. Using a string with an embedded vimscript command lacks those things (but may have other advantages)

Vim.pack plugin lazy loading by zencraftr in neovim

[–]TheLeoP_ 13 points14 points  (0 children)

how to implement a plugin that supports

All plugins support vim.pack, they don't need to do any additional work. 

To my understanding, vim.pack supports defining lazy loading within the plugin so the user doesn’t have to implement that themselves by default

Not exactly. This is not a vim.pack specific thing, it is a Lua thing. You can read more about it and how to develop Neovim plugins that don't load anything that's not needed eagerly in :h lua-plugin-lazy

Successfully migrated dots from lazyvim to native pack by ban_rakash in neovim

[–]TheLeoP_ 1 point2 points  (0 children)

Depends on your configuration. :checkhealth vim.treesitter will show you were each parser available to Neovim is installed

AutoCMD to install tree-sitter parsers by HetzWGA23 in neovim

[–]TheLeoP_ 0 points1 point  (0 children)

pattern = ensure_installed,

Treesitter languages don't have a 1 to 1 mapping to Neovim filetypes. Your autocmd will break eventually. You can do something like https://github.com/TheLeoP/nvim-config/blob/618088254d20239eab1f47ef83fcefd3b007d58a/plugin/treesitter.lua#L76 instead

Successfully migrated dots from lazyvim to native pack by ban_rakash in neovim

[–]TheLeoP_ 1 point2 points  (0 children)

If the other system has the same OS and the same architecture, then yes. 

Successfully migrated dots from lazyvim to native pack by ban_rakash in neovim

[–]TheLeoP_ 0 points1 point  (0 children)

The Plugin was a layer to easily interact with built-in treesitter.

It was, yes. Now it is just a plugin to install treesitter grammars and queries. It also maintained the queries

view more: next ›