Do you use in your plugin mappings?

I have a question for you plugin developers (but I am interested also in
a user's perspective). What do you think is the best approach to deal
with a conflicting mapping (i.e., a mapping already defined elsewhere)
in a plugin?

I currently define my plugin's mappings with <unique>, but from time to
time users report `E227: mapping already exists` errors as bugs, so I am
not sure that this is the best approach.

Btw, "do not define any mapping in a plugin" is not an answer. My
plugins already have such an option, but for some plugins providing
mappings by default is the natural choice.

Lifep.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.