neovim-ui
nvim-treesitter-textobjects
neovim-ui | nvim-treesitter-textobjects | |
---|---|---|
5 | 87 | |
83 | 1,914 | |
- | 3.7% | |
0.0 | 8.5 | |
about 3 years ago | 4 days ago | |
Lua | Scheme | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
neovim-ui
- Posibility of UI library for neovim?
-
Neovim - Build UI using nui.nvim
mjlbach/neovim-ui
-
Neovim v0.5
I understand the frustration (making neovim more cohesive is definitely a goal). It sounds like coc provides the UI you are used to, so there's no harm in sticking with that!
Many of our users explicitly don't want automatically called functions that would slow down the editor (autocommands that map signature requests to the language server, for example), so by nature neovim's core implementation is extremely conservative.
One thing I would like to do, is make the automatic pop-ups for signature easier to implement with our current handler, which means a plugin like signature-x could use our upcoming lsp.config option to configure it's borders (https://github.com/neovim/neovim/pull/14681), and match the rest of the UI.
I also have another project I was working on before the 0.5 stabilization phase (https://github.com/mjlbach/neovim-ui). The goal with this is to have composable/overridable UI elements built into core (which we would use for our internal lsp functions), that can be used (or overridden) by UI plugins.
In summary, I think the likelihood of autocompletion (and generally auto-anything) being built-into core is very small, but providing the APIs in neovim core to make snippets - autocompletion - automated UI elements easier for plugin authors is a high priority.
-
Plugin unification
Yep, I started working on this awhile ago https://github.com/mjlbach/neovim-ui but put it on hold for 0.5 stabilization.
-
status of neovim popup windows
I am working on this, but it will probably have to wait until after the 0.5 release (I don't know when this will be). This is part of the larger UI effort in neovim-ui which is currently glorified vaporware. As far as I know, TJ, Smolck, and I are the only ones who have expressed interest in fixing this.
nvim-treesitter-textobjects
-
Use treesitter to jump to next argument without going into nested function calls?
I was hoping to use nvim-treesitter-textobjects to jump to the next argument via something like this:
-
Code navigation ctags/cscope/gnu global alternative?
You want to look at nvim-treesitter-textobjects. It let's you define keymaps for navigating text objects defined by treesitter and you can also use them with commands like d, c and so on.
-
My Favorite Vim Oneliners for Text Manipulation
Thank you! It looks like nvim-treesitter-textobjects is a good plugin to start with:
https://github.com/nvim-treesitter/nvim-treesitter-textobjec...
-
How to move between the topmost/root node in treesitter?
I'm aware of nvim-treesitter-textobjects and I suspect my answer lies in this plugin, but is there a way to move between root nodes that is agnostic of the node type?
-
Manipulating and moving between function arguments in Neovim
Thanks! I just started using https://github.com/nvim-treesitter/nvim-treesitter-textobjects, and it works as a charm.
-
Searching for plugin to provide granular treesitter visual mode navigation
nvim-treesitter-textobjects
-
Vim Tip - Jump to start of function or code block
In this case, reading here is probably a good start: https://github.com/nvim-treesitter/nvim-treesitter-textobjects
-
Getting v(a|i)B working in Ruby?
Have a look at https://github.com/nvim-treesitter/nvim-treesitter-textobjects. Set up the @block.inner and @block.outer textobjects and it should work.
-
How do you jump to the beginning of a function
nvim-treesitter-textobjects lets you jump to (for instance) functions more accurately than with a regex-based approach using ]f
Or even better, one can use nvim-treesitter-textobjects. It already provides function/class selection and go-to functionality out-of-the-box.
What are some alternatives?
popup.nvim - [WIP] An implementation of the Popup API from vim in Neovim. Hope to upstream when complete
vim-multiple-cursors - True Sublime Text style multiple selections for Vim
nui.nvim - UI Component Library for Neovim.
nvim-treesitter-refactor - Refactor module for nvim-treesitter
guihua.lua - A GUI library for Neovim plugin developers
targets.vim - Vim plugin that provides additional text objects
TypeScriptToLua - Typescript to lua transpiler. https://typescripttolua.github.io/
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
nvim-lspconfig - Quickstart configs for Nvim LSP
vim-textobj-user - Vim plugin: Create your own text objects
nvim-lsputils - Better defaults for nvim-lsp actions
vscode-neovim - Vim mode for VSCode, powered by Neovim