Skip to content

Error stopping job #15

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.

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

Closed
AckslD opened this issue Jun 16, 2021 · 9 comments
Closed

Error stopping job #15

AckslD opened this issue Jun 16, 2021 · 9 comments

Comments

@AckslD
Copy link

AckslD commented Jun 16, 2021

Not sure I'm doing something wrong but when I try to use spectre nothing shows up in the preview and when I enter a path and leave insert mode I get the following error:

Error detected while processing InsertLeave Autocommands for "<buffer=3>":                                                                                                    
E5108: Error executing lua ...ck/packer/start/nvim-spectre/lua/spectre/search/base.lua:124: attempt to call method 'stop' (a nil value)

Any idea why this might be happening?

Looking at the code, it does check that the plenary Job is not nil but for some reason it doesn't have the method stop.

@windwp
Copy link
Collaborator

windwp commented Jun 16, 2021

what is your setup function?
the stop function come from plenary lib so it should have if job is not nil.
are you to update plugin?

@AckslD
Copy link
Author

AckslD commented Jun 16, 2021

I don't call setup actually, is that required? I only for now have a mapping to

:lua require("spectre").open()<CR>

I'm currently on 4ee33ae

@windwp
Copy link
Collaborator

windwp commented Jun 16, 2021

you need to call setup.

@windwp windwp closed this as completed Jun 16, 2021
@AckslD
Copy link
Author

AckslD commented Jun 16, 2021

@windwp since this is only under Customisation in the README and not under Usage I assumed that it was only needed if one wants to change the default settings.

Anyway, I added it to my config but I have the same behaviour.

@windwp
Copy link
Collaborator

windwp commented Jun 16, 2021

i cannot reproduce your issue.
so can you test it with a minimum config or at least provide a detail to how to get that issue.

@windwp
Copy link
Collaborator

windwp commented Jun 18, 2021

sorry i found a problem you are using ripgrep 13
just update and check again
BurntSushi/ripgrep#1892
nvim-telescope/telescope.nvim#907

@AckslD
Copy link
Author

AckslD commented Jun 19, 2021

Thanks for coming back to this @windwp, what requires an update? ripgrep, neovim, telescope or spectre? I currently have:
ripgrep: 13.0.0
neovim: v0.5.0-dev+1425-g7da86f55a
telescope: 6ac5ee0
spectre: 4ee33ae

@windwp
Copy link
Collaborator

windwp commented Jun 19, 2021

just update spectre

@AckslD
Copy link
Author

AckslD commented Jun 19, 2021

Yep that worked, apologies. Don't know why but when I did PackerUpdate it didn't update spectre for some reason, but I had to manually pull to get the latest commits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants