1

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?

  • You've submitted (and then withdrew) the same imprecise question already on SO. Just repeating it here won't make it better... – Ingo Karkat Sep 25 '14 at 8:55
2

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.

  • +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 Sep 25 '14 at 11:39
  • For that, it probably defines an :autocmd VimEnter *. Is this defined? Does it appear in the log file? – Ingo Karkat Sep 25 '14 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 Sep 25 '14 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 Sep 25 '14 at 12:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.