Replies: 1 comment 1 reply
-
That's awesome! I figured using one of the rendering plugin's main advantages for this use case would be the ability for you to avoid maintaining an entire UI layer with its own set of issues, pitfalls, and maintenance burden. Though I get not requiring the dependency for users and shipping something complete out of the box if that's what you're going for. There's something like that but only based off of buffer option values, i.e. I can add support for it to be a function similar to |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
👋
We have been working on a community fork of obsidian.nvim, since the original author have not been actively maintaining it (but huge respect agian).
I have been looking through the issues for some low hanging fruits that we can get for the project to live more sustainably and epwalsh/obsidian.nvim#664 came up.
So now the default behavior would be to check this plugin and markview's existence. It will just turn off the builtin renderer if found. Avoiding user confusion.
But I want to ask if there's a way to turn off this plugin's rendering functionality, like a buffer local variable that this plugin checks before enabling itself, I know blink.cmp does this, https://cmp.saghen.dev/configuration/reference. This avoids the conflict if user of obsidian.nvim if they want to just use the builtin renderer if in obsidian vaults and want to use this plugins outside of the vaults.
Beta Was this translation helpful? Give feedback.
All reactions