How to determine what a "bare-bones" vim is for a plugin

Hello,

Some plugin authors understandably require that any issue reports to be
reproducible on a "bare-bones" vim. But that plugin might be requiring
a vim that has more capabilities than one started with "gvim -u none -U
NONE". As an example, fugitive.vim is inoperable in such a gvim, and
silently so (no error messages).

So, in general, given a plugin, how does one determine what is the
"bare-bones" vim it's author has assumed?

Thanks,

--Suresh

--
--
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.