How does this compare to obsidian.nvim? #195
Closed
einarpersson
started this conversation in
General
Replies: 1 comment
-
Hey! We support all of your points except for templating and hook. I'd recommend using both obsidian.nvim and oxide and doing so by turning off obsidian.nvim completions. Obsidian.nvim is really good for syncing Obsidian and neovim and supports other obsidian specific features like templating and hooks |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi!
I currently use the following in tandem
I like the idea of separating the UI from the underlying logic. I am very happy with
render-markdown.nvim
doing the rendering, and I have disabled rendering forobsidian.nvim
.With all that said, I guess my question is in the title. How does this thing (markdown-oxide) compare to
obsidian.nvim
? I understand that the scope is broader / different (I like the idea of leveraging the LSP). But personally I ask, can I replace obsidian.nvim with this? The website says that it is highly compatible with obsidian but I'm not sure what it means. Does it provide the basic functionalities as well?Eg.
I see some features listed as available and others not yet (eg links to headings). But I guess my general question is: If I want to manage my obsidian vault in neovim, could I do that with just this plugin and not obsidian.nvim (in tandem with rendering plugin)? And does using this plugin have some extra benefit that you know of, right off the bat?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions