^M error when PluginSearch ,Please help me~

VundleVim / Vundle.vim

Vundle, the plug-in manager for Vim

http://github.com/VundleVim/Vundle.Vim

MIT License

23.94k stars 2.57k forks source link

^M error when PluginSearch ,Please help me~ #914

Open THtianhao opened 4 years ago

THtianhao commented 4 years ago

Do you have this question? When i input PluginSearch xx and Tab ,I will occur some error like this:

:PluginSearch ...
Error detected while processing function vundle#scripts#complete[6]..<SNR>58_load_scripts:
line    7:
E15: Invalid expression: <html>^M
E15: Invalid expression: <html>^M
Error detected while processing function vundle#scripts#complete:
line    6:
E714: List required
:PluginSearch 0

davidlowryduda commented 4 years ago

Yes, I confirm this behaviour. This is caused by the fact that the vim-scripts mirror api has been deprecated. (See https://vim-scraper.github.io/). As a result, the stashed json file of available vim scripts is just a HTML file containing info that the resource has moved, and the parser fails.

The appropriate thing to do is to remove this functionality from vundle.

michaelkruglos commented 4 years ago

@davidlowryduda I strongly disagree. There's another api which can be implemented. https://vimawesome.com/api/plugins?query= Example request with fetch on node:

var fetch = require('node-fetch')

fetch("https://vimawesome.com/api/plugins?query=golang&page=1", {
  "credentials":"omit",
  "headers":{
    "accept":"application/json, text/javascript, */*; q=0.01",
    "accept-language":"en-US,en;q=0.9",
    "sec-fetch-mode":"cors",
    "sec-fetch-site":"same-origin",
    "x-requested-with":"XMLHttpRequest"
  },
  "referrer":"https://vimawesome.com/",
  "referrerPolicy":"no-referrer-when-downgrade",
  "body":null,
  "method":"GET",
  "mode":"cors"
})
  .then(result=>result.json())
  .then(json=>console.log(json)) ;

erasmussen1 commented 4 years ago

Yes, I confirm this behaviour. This is caused by the fact that the vim-scripts mirror api has been deprecated. (See https://vim-scraper.github.io/). As a result, the stashed json file of available vim scripts is just a HTML file containing info that the resource has moved, and the parser fails.

The appropriate thing to do is to remove this functionality from vundle.

Yes, I confirm this behaviour. This is caused by the fact that the vim-scripts mirror api has been deprecated. (See https://vim-scraper.github.io/). As a result, the stashed json file of available vim scripts is just a HTML file containing info that the resource has moved, and the parser fails.

The appropriate thing to do is to remove this functionality from vundle.

(I'm not a plugin expert) Is there a workaround for this issue?

davidlowryduda commented 4 years ago

@erasmussen1 It's not quite clear what you mean by workaround. If you don't use PluginSearch, then vundle works fine. I might call "google for a plugin you're interested in" a viable workaround. Did you have another meaning in mind?