obsidian.nvim vs markdown-oxide (lsp)

[vaibhav423]

i am using markdown-oxide , never tried .
anyone who is willing to argue why i should change to obsidian.nvim

[neo451]

to preface I have not used markdown-oxide extensively either

but you get these:

1. extensive lua scripting for any task you like, this plugin provide things for paring markdown stuff, refactoring documents and manage your vault on a more granular level (many actions in the works)
2. things like pasting smartly into markdown (images, html, attachments) and managing attachments and templates, are all outside of the scope of an LSP server, if you care about these you use obsidian.nvim
3. you get a mobile app for free, and I am implementing Headless Sync #716 as we speak

also reference this answer: #52 (comment)

In short this plugin has more scope than a markdown LSP, it works through LSP because it is more intuitive and reduce friction. So obsidian.nvim and markdown LSPs are not 1 to 1 comparable

Also side note, since neovim can resolve multiple LSP servers on the same buffer, no harm enable both in a buffer to see which makes sense, you can also reference this to disable some features of obsidian.nvim and just use markdown-oxide if you find them better:
https://github.com/orgs/obsidian-nvim/discussions/538

[vaibhav423]

markdown-oxide , provides pasting / completion . for templates i use lua snippets . and git for sync. and features like follow link , back link . unreferenced link are present in the lsp itself .

[neo451]

1. not sure what pasting capability you are referring to, that sounds unlikely to be done by a LSP and I don't find anything on the project readme
2. yes templates now is not really as powerful as lua snippets, and git is ofc a good choice for sync, you have a good enough setup that everything I can say is a bit pale, and some might not even interest you, since I don't even now what excites, I'll just list anything that comes to mind why this repo makes some interesting efforts that will eventually make everything a bit smoother, just for whoever reads this question:
3. for templates draft: etlua for templater like template #284 a full template engine based on lua expressions, proven by the obsidian templater plugin to be quite a powerful idea. To me: templater > luasnip > current obsidian-compatible template
4. for pasting feat: Obsidian paste can handle html to markdown conversion #558 eventually it will turn into quite a smart and configurable clipboard handler, for every possible thing that can be pasted (actual attachment content, url to attachment, path to attachment, raw html content, or raw url link), you can choose to link it, attach it in the vault, or embed it inline
5. LSP hovers can not be fully configurable, since it don't have access to neovim APIs, but this project can have proper hover editor feat: Embed Note Preview #305 (comment)
6. This plugin is compatible with some more obsidian specific markdown stuff that other markdown LSPs don't, like https://help.obsidian.md/links#Link+to+a+block+in+a+note and %% style comments, I am also planning to start contributing to tree-sitter-markdown to make these support more smooth, this is also a perk, this plugin has access to full markdown AST easily thanks to neovim, so many things are easy to build
7. https://github.com/obsidian-nvim/obsidian.nvim/wiki/Images and it will be even better once neovim lands its image API.