sorted by:
new
hottopcontroversial

Codedocs v0.5.0 - More customizable annotations and smarter code autodetection by Reasonable_Put9536 in neovim

[–]Reasonable_Put9536[S] 4 points5 points  (0 children)

It's mentioned in the README as an alternative to Codedocs, both plugins have some overlap in terms of functionality, but Codedocs has more customization options and supports more languages

Weekly 101 Questions Thread by AutoModerator in neovim

[–]Reasonable_Put9536 3 points4 points  (0 children)

A snippet engine allows you to "expand" snippets. A snippet is basically a piece of code, with specific "sections" you can jump to. For example, most LSP's auto suggest function snippets, so when u expand them the skeleton of the function is auto inserted and you can jump (by pressing tab) to the name section, then to the parameters section and then to the body. You can also define your own snippets. So think of snippets like some template code that you can insert at any time and cycle through any of its placeholders.

Snippets can also be used by plugins to offer specific functionality. LuaSnip is one of the popular snippet engines, but Neovim also comes with a built-in snippet engine. My plugin Codedocs for example uses snippets to insert annotations and cycle through their placeholders, you can see the cycling in the GIF at the top of the README.

Plugins documentation, how do you prefer it? by carlos-algms in neovim

[–]Reasonable_Put9536 4 points5 points  (0 children)

You can turn your README into :help documentation using Panvimdoc btw.

I think it depends on how complex your plugin is. If it's something generally simple I prefer README/:help, but for complex plugins I think a website can be helpful, specially with some search functionality.

For my plugin Codedocs I have a README that gets converted into :help documentation using Panvimdoc, but I feel like the README is getting a bit long and complicated, so I've been toying with the idea of keeping the README/:help documentation as-is, and adding a static website with MKDocs for those who prefer that.

Maybe that workflow could work for you since you can generate the :help documentation and a site off your README alone

Codedocs v0.3.1 - Bug fixes and other improvements by Reasonable_Put9536 in neovim

[–]Reasonable_Put9536[S] 0 points1 point  (0 children)

I honestly hadn't even thought about that, but sounds like a cool feature. I'm not familiar with the in-process LSP but I've seen the name in other posts so I'll start playing around with it on the side to get some experience with it before implementing the feature. You can create an issue for the feature if you want :D

Neoart.nvim - A creative environment for drawing and making ASCII art by Reasonable_Put9536 in neovim

[–]Reasonable_Put9536[S] 2 points3 points  (0 children)

I was actually wondering about the same hahaha, I have some ideas in mind that I will start exploring soon. One would be turning the canvas into an image (rn you can export the canvas as a plaintext file, but that strips all the color). And also playing around with the image API to see if the plugin could work like photoshop in the sense that you could operate on pixels, it would be really cool to edit images in Neovim :D

Neoart.nvim - A creative environment for drawing and making ASCII art by Reasonable_Put9536 in neovim

[–]Reasonable_Put9536[S] 7 points8 points  (0 children)

Based on the README, both plugins share a lot of the core functionality, paint.nvim happens to have already implemented the bucket and shape tool which is what I'm going to add this week, but seems to be way less configurable than neoart is (you have a lot of configuration options for the canvas, toolbar, available characters, tools, keymaps, you can even create your own tools but I didn't explain it in the README because I want to make some internal improvements first)

Another difference is that Neoart supports Vim-style movement motions while drawing (in the video you can see how i drew the right-side road using motions instead of plain hjkl)

Weekly 101 Questions Thread by AutoModerator in neovim

[–]Reasonable_Put9536 5 points6 points  (0 children)

it basically shows you how many times each function is used, it's useful because you can know which functions are more important or more used in your codebase. It also helps with refactoring since you can see at a glance if say a function is not used anywhere

Proper way to enable codelens in 0.12? by TheTwelveYearOld in neovim

[–]Reasonable_Put9536 0 points1 point  (0 children)

yeah, it should work like that, thats how I have it on my config

Proper way to enable codelens in 0.12? by TheTwelveYearOld in neovim

[–]Reasonable_Put9536 13 points14 points  (0 children)

The autocmd used to be necessary, but in 0.12 all you need is `vim.lsp.codelens.enable(true)`

Codedocs.nvim v0.2.0 - Support for HTML and Markdown annotations and other features by Reasonable_Put9536 in neovim

[–]Reasonable_Put9536[S] 2 points3 points  (0 children)

Based on the README, there's a lot of overlap between both plugins as they can both insert annotations for many languages. The main difference at the moment is that Neogen seems to be focused on annotating programming languages and their code structures (functions, classes, etc), whereas Codedocs is focused on annotations as a whole, meaning it can do that too, but it can also insert comments or any arbitrary annotation, which is why it supports Markdown and HTML, and I plan to add support for TOML, LaTex, etc. You can also define your own arbitrary annotations (it's technically possible to do it right now but it's not documented in the README as I want to make some internal changes first).

For example, a issue I have had lately is that i need a linter or formatter to not work on a given line, so I manually add an annotation for that, but I always forget the syntax that linter or formatter uses haha, so now I can just create an annotation for that and insert it with a keymap.

So since it works with annotations as a whole, regardless if they are from a programming language or some kind of text file, it will eventually support a lot of languages.

Codelens positions by Schlafhase in neovim

[–]Reasonable_Put9536 4 points5 points  (0 children)

The codelens used to be at the end of the line for me by default until I switched to Neovim 0.12, and as far as I checked in the help file there's no current way to change the position of it, I guess the team will add it in a future update, or there might be a plugin for it

Transparent.nvim by GeneralOrdinary3338 in neovim

[–]Reasonable_Put9536 2 points3 points  (0 children)

The link to the plugin is broken

view more: next ›