Option to turn off default instructions 'warning'

[marty-oehme]

By default the plugin displays a vim.notify message informing the user of having to move all changes to the left and using :cq to quit without changes.

I think this is useful 'tutorialization' when starting to use the plugin but in my case it requires another press to acknowledge each time:

There are two issues I have with the current version:

1. It would be nice to have the option to turn off the instructions once we know how the tool works.
2. And I am not sure if notify.WARN is the appropriate level to set the information at?

I will post a PR with a simple fix using the same vim.g.jj_diffconflicts_<option> pattern as the marker_length setting,
but ultimately perhaps it would be better to switch the plugin initialization to use a setup function like many other lua plugins?

[rafikdraoui]

Hello!

I made a PR that should address this issue: #6. Let me know if it works for you.

In my case it requires another press to acknowledge each time

Ah, yes. That must be very annoying! I had not encountered this before. I assume you have set cmdheight=0?

And I am not sure if notify.WARN is the appropriate level to set the information at?

It was set at the WARN log level, otherwise the message would disappear immediately.

That said, I noticed that the message now also disappears immediately even at WARN level, so maybe this is unrelated to the log level 🤔 I have draft PR #7 to address that, but it breaks all the screenshot tests, so I'll have to think about what I want to do about that!

Perhaps it would be better to switch the plugin initialization to use a setup function like many other lua plugins?

I like the idea of using the built-in way of leveraging the standard Vim runtime mechanism to activate the plugin, instead of "reinventing" the feature by manually implementing it. That said, I'm not entirely opposed to moving to a setup()-based workflow. But that would be a breaking change for existing users, and I don't want to do that unless there's a compelling reason.

[marty-oehme]

Ah, yes. That must be very annoying! I had not encountered this before. I assume you have set cmdheight=0?

Exactly!

It was set at the WARN log level, otherwise the message would disappear immediately.

I think this is less substantial for me, it was more of an intuitive expectation. But I did expect it would be connected to keeping the message on-screen at the start.

I'm not entirely opposed to moving to a setup()-based workflow. But that would be a breaking change for existing users, and I don't want to do that unless there's a compelling reason.

No worries, I had the same thoughts for a plugin I made as well. In my case, it interfered with lazy loading but I just tried and I can easily lazy load your plugin with my plugin manager nonetheless. (I think I've just become so accustomed to the neovim lua-setup way of plugin loading that for a moment it seemde archaic to vim.g 😉).