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

Hi 'Suresh!

On Fr, 17 Mär 2017, 'Suresh Govindachar' via vim_use wrote:

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

As maintainer of vim-airline that is totally understandable and I
request the same if the bug is not reproducible for me. It happened to
often that someone comes over, stating "I started using Vim 1 month ago,
installed vim-spf13 and when switching buffers airline is not
refreshed."

I expect a litte more from the bug reporter, e.g. trying to reproduce
this with a sane minimal configuration, as I am not going to debug a
multi thousands line vim configuration.

Best,
Christian
--
Wenige Dinge auf Erden sind lästiger als die stumme Mahnung, die von
einem guten Beispiel ausgeht.
-- Mark Twain (eigl. Samuel Langhorne Clemens)

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