Only for installing and updating, it’s honestly not really feasible for instance plugins via a UI due to the configuration being inlined with the plugin declaration. It’s not too bad once you get used to it.
Specifics will differ based on your colorscheme, but the end goal is always the same - set telescope border colors to blend with the rest of the telescope ui.
LSP maybe portable with it’s config if the LSP themselves are independent. Checkout Mason which seems to make it easier to bundle neovim and “portable” LSP. There was another project similar to Mason with some more features, but I forgot it’s name. So search around to see if that fits your requirements.
Just use the NeoVim defaults and then if something is bothering you or missing, rebind it. Most of the defaults have been totally legit for decades, and everyone speaks in terms of them. At the end of the day, your job is to build muscle memory one way or another
hey! I’m more than willing to devote some of my free time to help more here. If any of the mods here want to have a chat with me, please reach out in DMs.
Prescript: I am by no means a programmer, and input to follow is likely useless.
Have you looked at Markdown plugins that otherwise align with what you are looking for to see if there are usable approaches to be adopted? Or maybe even contribute a PR to one of those projects for Asciioc support?
In any case, I recently fell in love with Asciioc and selfishly hope you are successful!
I had a similar idea, however i haven’t seen a markdown plugin, that is well maintained and at the same time simple enough, so that the core, in this case markdown, can easily be replaced with a completely different engine, asciidoctor.
Any recommendations for that?
I also thought about changing neorg, but the missing support for treesitter is a k.o. for asciidoc.
neovim
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.