panvimdoc VS nvim-neoclip.lua

Vim Doc to markdown! IDK who's doing that, but people prefer other way around markdown to vimdoc using https://github.com/kdheepak/panvimdoc

If someone wants similar functionality and they are okay with depending on pandoc instead, I have this repo that make be of relevance: https://github.com/kdheepak/panvimdoc. It also works as a github action, so you can add to a .github/workflows/docs.yml file and forget.

If you're using panvimdoc you can put and comments to exclude parts from the generated vimdoc. See my plugin's README.md

Macro history integrated with Telescope is something nvim-neoclip does, if you're interested in that. The relevant part of the README can be found here.

Also has an integration with fzf-lua to fuzzy find the history of yanks a-la nvim-neoclip.lua:

I've worked on some updates to neoclip which is a clipboard manager with telescope and fzf-lua integrations. I thought I'd also write a bit about the implementation for the new features since I found this quite fun and interesting and maybe it can be of interest for others :)

There's also neoclip :)

This is now implemented in this PR. It seems to work for me and I'm already using it but will wait a bit to merge. If anyone has some thoughts or issues I'd be happy to hear it.

I've seen some people preferring to use fzf-lua over telescope. I don't really use it my self atm, but I thought as a good way to find out how it works, is to support it in my clipboard manager neoclip.

Thanks, just trying to understand the differences and if it's worth updating my own plugin neoclip to also support fzf-lua additionally to telescope :)

But maybe there is no need for duplication. In your view, just so I can get an idea, what do you think in the README of my latest (somewhat popular) plugin neoclip should move from the README to the vimdoc?

Keybind to paste content directly instead of populating register (or both). (#9)