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.

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

Hiding timeout error for one engine #1828

Open
sevospl opened this issue Feb 4, 2020 · 5 comments
Open

Hiding timeout error for one engine #1828

sevospl opened this issue Feb 4, 2020 · 5 comments
Labels
Projects

Comments

@sevospl
Copy link

@sevospl sevospl commented Feb 4, 2020

Is it possible to hide/disable timeout error for one engine?

@unixfox

This comment has been minimized.

Copy link
Contributor

@unixfox unixfox commented Feb 4, 2020

Just set the default timeout to a large number?

@sevospl

This comment has been minimized.

Copy link
Author

@sevospl sevospl commented Feb 4, 2020

Just set the default timeout to a large number?

The thing is I want to decrease the timeout as much as possible to make my searching even faster. There are some engines that are irrelevant to me and I'd be ok with "hit or miss", but the whole timeout thingy is annoying.

@dalf dalf added the enhancement label Feb 4, 2020
@virtadpt

This comment has been minimized.

Copy link

@virtadpt virtadpt commented Feb 4, 2020

It might make more sense to disable the search engines you don't care about in the searx/searx/settings.yml file.

@sevospl

This comment has been minimized.

Copy link
Author

@sevospl sevospl commented Feb 4, 2020

It might make more sense to disable the search engines you don't care about in the searx/searx/settings.yml file.

Yeah, I disabled some but there are some that I'd rather keep with "hit or miss" :)

@virtadpt

This comment has been minimized.

Copy link

@virtadpt virtadpt commented Feb 4, 2020

Okay, that makes sense.

@asciimoo asciimoo added this to Milestone #1 - Frontend in v1.0.0 Feb 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
v1.0.0
  
Milestone #1 - Frontend
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.