Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
THtianhao opened this issue Dec 10, 2019 · 13 comments
Open

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

THtianhao opened this issue Dec 10, 2019 · 13 comments

Comments

@THtianhao
Copy link

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
Copy link

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
Copy link

@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
Copy link

erasmussen1 commented Jan 12, 2020 •
edited
Loading

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
Copy link

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

@drosan-dev
Copy link

I have same problem

@Rimvel-hub
Copy link

I also have this problem. Is there a solution?

@San4ito
Copy link

San4ito commented Apr 20, 2020

Me too, and i don't know how to solve this problem.

@r0mille
Copy link

r0mille commented May 10, 2020

plus 1

@davidlowryduda davidlowryduda mentioned this issue May 12, 2020
Open
@kmuzalewska
Copy link

problem still present

@Unixware
Copy link

Unixware commented Jan 2, 2021

its the f year 2021 still this issue.. for LOLz

@huberemanuel
Copy link

Same here

@mariogarridopt
Copy link

i have the same problem, looks like its not gonna be solved

@antoniopaolini
Copy link

Maybe this solve the problem.
Also see this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests