kommentary
language-server-protocol
kommentary | language-server-protocol | |
---|---|---|
14 | 121 | |
533 | 10,725 | |
- | 0.9% | |
2.9 | 8.7 | |
5 months ago | about 21 hours ago | |
Lua | HTML | |
MIT License | Creative Commons Attribution 4.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.
kommentary
-
A pragmatic approach to migrating from VSCode to Neovim
Indent-blankline to draw indentation guides, nvim-autopairs to automatically complete pairs of brackets and quotes (I didn’t know I couldn’t live without it), nvim-ts-autotag to autocomplete pairs of tags as well, targets.vim to target what is inside or outside the mentioned pairs and vim-surround to manage all those pairs with few keystrokes. Kommentary to comment and uncomment lines of code, nvim-cursorline to help locate where the cursor is and nvim-colorizer because I am cheeky. Vim-abolish is definitely an interesting one. I decided to install it because of its case coercion capabilities, but it can do much more than that.
-
Question: Is it a requirement that plugins written in Lua require you to call the setup function?
Here’s an example of a lua plugin with no setup function
-
TakeTuesday: Comment.nvim tutorial
The one I use is kommentary.nvim. A) It works, and with embedded code too, but also b) the Lua underneath it is really good. It’s well-commented, tested, and just generally a good resource to learn Lua from (or at least it has been for me.)
-
Comment.nvim: new stuff that will make you Rick Roll.
A bit unrelated, but I wrote some tests for kommentary that might inspire you to create a test suite for this plugin too.
-
Comment.nvim: Simple and powerful comment plugin for neovim. Supports commentstring, dot repeat, left-right/up-down motions, hooks, and more
Dot repeat https://github.com/b3nj5m1n/kommentary/issues/41
-
Comment C/C++ line or block
I'm still using the tpopes plugin, so I don't really know about the Lua versions 😅. But I have heard good things about kommentary
-
nerdcommenter seems to better figure out what comment syntax to use than vim-commentary, but i like vim-commentary more at everything else
I've been using b3nj5m1n/kommentary . I's uses are similar to vim-comentary . It has option to use only single line comments . This can be used to avoid /* ... */ . You can try that out .
-
Aspiring plugin authors: look at kommentary
b3nj5m1n/kommentary is one that is relatively small, but big enough to be interesting. It is also *insanely* well documented and the overall code quality seems good to me.
-
commented.nvim, a commenting plugin that actually works with count.
I need a comment plugin that works in normal mode and virtual mode and accepts count. Neither does kommentary and nvim-comment provide counts, therefore I decided to write one for myself.
-
Custom keymap function does not work with `<Plug>` commands
I can import this function and use it with all my custom keybindings. However, it doesn't custom keybindings I want to use for the Kommentary plugin.
language-server-protocol
-
Ollama is now available on Windows in preview
But these are typically filling the usecases of productivity applications, not ‘engines’.
Microsoft Word doesn’t run its grammar checker as an external service and shunt JSON over a localhost socket to get spelling and style suggestions.
Photoshop doesn’t install a background service to host filters.
The closest pattern I can think of is the ‘language servers’ model used by IDEs to handle autosuggest - see https://microsoft.github.io/language-server-protocol/ - but the point of that is to enable many to many interop - multiple languages supporting multiple IDEs. Is that the expected usecase for local language assistants and image generators?
-
The Mechanics of mutable and immutable references in Rust
If you tried writing code like the one above, your Rust LSP should already be telling you that what you're doing is unacceptable:
-
A guide on Neovim's LSP client
A language server is an external program that follows the Language Server Protocol. The LSP specification defines what type of messages a language server can receive, and also how it should respond. The idea here is that any tool that follows the LSP specification can communicate with a language server.
-
The IDEs we had 30 years ago and we lost
> There's a strange dance of IDEs coming and going, with their idiosyncracies and partial plugins.
The Language Server Protocol [1] is the best thing to happen to text editors. Any editor that speaks it gets IDE features. Now if only they'd adopt the Debug Adapter Protocol [2]...
[1] https://microsoft.github.io/language-server-protocol/
[2] https://microsoft.github.io/debug-adapter-protocol/
-
The More You Gno: Gno.land Monthly Updates - 6
The Gno Language Server (gnols) is an implementation of the Language Server Protocol (LSP) for the Gno programming language. It is similar to the equivalent “gopls” project for Go, as they can be plugged into your code editor through extensions and allow you to access handy features, such as autocompletion, formatting, and compile-time warnings/errors. Gnols makes writing code simpler, working with several editors to suit your preferences. To try it out, visit the CONTRIBUTING.md file, which contains instructions to get you started. Our current documentation targets Vim, Neovim, and SublimeText, but can likely be used with any editor that supports LSP. Feel free to contribute to improving Gnols and adding more features. It’s well-written, and simple to dive into the code and add more capabilities.
-
LSP could have been better
Honestly, you should read some of the docs [0] if these are the sorts of questions you're asking.
[0] https://microsoft.github.io/language-server-protocol/
-
Show HN: Postgres Language Server
hey HN. this is a Language Server[0] designed specifically for Postgres. A language server adds features to IDEs (VSCode, NeoVim, etc) - features like auto-complete, go-to-definition, or documentation on hover, etc.
there have been previous some attempts at adding Postgres support to code editors. usually these attempts implement a generic SQL parser and then offer various "flavours" of SQL.
This attempt is different because it uses the actual Postgres parser to do the heavy-lifting. This is done via libg_query, an excellent C library for accessing the PostgreSQL parser outside of the server. We feel this is a better approach because it gives developers 100% confidence in the parser, and it allows us to keep up with the rapid development of Postgres.
this is still in early development, and mostly useful for testers/collaborators. the majority of work is still ahead, but we've verified that the approach works. we're making it public now so that we can develop it in the open with input from the community.
a lot of the credit belongs to pganalyze[1] for their work on libg_query, and to psteinroe (https://github.com/psteinroe) who the creator and maintainer of the LSP.
[0] LSP: https://microsoft.github.io/language-server-protocol/
[1] pganalyze: https://pganalyze.com/
-
Refactoring tools
See: https://github.com/microsoft/language-server-protocol/issues/1164
-
Nx Console gets Lit
The nxls is a language server based on the Language Server Protocol (LSP) and acts as the “brain” of Nx Console. It analyzes your Nx workspace and provides information on it, including code completion and more.
-
How to configure vim like an IDE
LSP stands for "Language Server Protocol", which defines how a language server and an editor (client) can communicate to provide code navigation, completion, etc. (source). Traditional IDE's would have something similar to this baked-in already, but proprietary to their software/language; whereas LSP is an open standard, so anything could implement it.
What are some alternatives?
nvim-comment - A comment toggler for Neovim, written in Lua
intellij-lsp-server - Exposes IntelliJ IDEA features through the Language Server Protocol.
vim-commentary - commentary.vim: comment stuff out
tree-sitter-org - Org grammar for tree-sitter
Comment.nvim - :brain: :muscle: // Smart and powerful comment plugin for neovim. Supports treesitter, dot repeat, left-right/up-down motions, hooks, and more
omnisharp-server - HTTP wrapper around NRefactory allowing C# editor plugins to be written in any language.
nvim-ts-context-commentstring - Neovim treesitter plugin for setting the commentstring based on the cursor location in a file.
tree-sitter - An incremental parsing system for programming tools
commented.nvim - Neovim commenting plugin in Lua. Support operator, motions and more than 60 languages! :fire:
magic-racket - The best coding experience for Racket in VS Code
tcomment_vim - An extensible & universal comment vim-plugin that also handles embedded filetypes
friendly-snippets - Set of preconfigured snippets for different languages.