2

I have installed the plugin vim startify which worked fine in my remote server where I use it. Something happened (I think an upgrade) and the plugin no longer seems to work!
But I don't get any error e.g. when vim starts.
How do you track down the problem in such cases?

1
  • You've submitted (and then withdrew) the same imprecise question already on SO. Just repeating it here won't make it better... Commented Sep 25, 2014 at 8:55

1 Answer 1

3

First, check that the plugin is correctly installed; its scripts must appear in :scriptnames.

Then, check what artifacts it defines (commands, mappings, autocmds), and verify they're there via :verbose map ... and :verbose command ..., :verbose autocmd ...

Finally, trigger the plugin functionality while capturing a log with vim -V20vimlog. In the log (or alternatively with :debugging), you can observe what the plugin is doing, and hopefully locate when and where it goes wrong.

4
  • +1.Very useful info. Concerning Finally, trigger the plugin functionality while capturing... how can I do that?The plugin is supposed to start as soon as I start vim
    – Jim
    Commented Sep 25, 2014 at 11:39
  • For that, it probably defines an :autocmd VimEnter *. Is this defined? Does it appear in the log file? Commented Sep 25, 2014 at 11:50
  • When I do :scriptnames: it does not appear as part of the list.When I do vim -V20vimlog I don't see any output.When I do :debug in vim I get:E471: Argument required
    – Jim
    Commented Sep 25, 2014 at 12:14
  • Actually I found the vimlog!I see the plugin mentioned, but I don't know what am I supposed to look for.
    – Jim
    Commented Sep 25, 2014 at 12:16

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .