Introduce sane defaults?

[TheMeaningfulEngineer]

@neo451
I would like to some time do a refresh of the README.md and ideally make some videos on some of the most common flows.
What are your thoughts on daring to define sane defaults for the project with regards to the optional dependencies?

minimal.lua starts with asking you to make a choice on the completion engine, and picker and renderer...
I think it would be a nicer end use experience to just provide a default so a new user has the shortest flow to a working obsidian.

[neo451]

Video is a great idea, I will do it in a few months, I mean if we do a series, we need more stuff to show, at least more lsp features.

I am not sure what your idea of "sane defaults" is, the minimal.lua is for debugging, not trying out the plugin, and the three things are all people are mostly likely already using and configured before using obsidian.nvim, how can we provide a default? we have checkhealth to warn if they are not using at least one, and we have [recommend] in readme, I don't know what more power do we have.

If we really choose for user, we are then making a distro like LazyVim, which is not a bad idea actually, obsidian.nvim + recommended plugins + all the plugins that are good for markdown editing

[TheMeaningfulEngineer]

This is where I'm coming from to perhaps make the motivations clear.
Whenever I want to try a complex plugin, I prefer to set up the environment of the tutorial in a sandboxed environment and the play around a replicating what the tutorial does and gradually doing my own experiments.
Once the plugin does what I wanted it to do, I perform a migration to my global config and integrate it into my overall flow.

That's the experience I'd like to offer new users.
Here's a way to quickly try it out.
You're free to use any other combination of settings if you're advanced but if you don't want to worry about pickers and completion tools, here use these they are as good as any.

the minimal.lua is for debugging, not trying out the plugin

Fair, but what's the recommended way to try it out? :)
That's what I'm aiming at.

[neo451]

This is a very inspiring workflow of yours, but here's some of my thoughts

1. not sure how many people share your workflow, I guess most folks does not, and few plugins I have seen offer a sandbox they use it for debugging, so that user's other plugins does not get in the way.
2. obsidian.nvim is "sandboxed" by default, it will not set any global keymaps, it will not really work outside of vault, and a vault is like a sandbox, with corresponding options and directory. It restricts itself pretty well, at least for me.
3. I started https://github.com/neo451/ObVim yesterday, inspired by your idea of choosing for the user, but a distro don't fit your need of trying out, because I think it is a chance for like a more complete markdown environment.

[TheMeaningfulEngineer]

Ok, closing.