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

Feature Request: Option to disable TextSouce from Top Level Search #90

Closed
hugosenari opened this issue Apr 23, 2017 · 4 comments
Closed

Comments

@hugosenari
Copy link

Actual Behaviour

All TextSource are Top Level and user can't choose remove from top level without disable plugin.

Expected Behaviour

When user enable any plugin with a TextSource
Then add it in Catalog tab to be enabled/disabled from Top Level
And add other way to access that TextSource:

  • Maybe creating an action to search in non Top Level sources;
  • Or just listing them in Sources and if user choose that source start searching using it
@bluss
Copy link
Member

bluss commented Apr 23, 2017

Yes. Since I've added ? to start free text, some plugins can use that and only produce results for ? prefix. I have a plugin in the works that uses it for firefox keyword search. I.e ?ddg search terms would search duck duck go if there is a ddg keyword for it.

@hugosenari
Copy link
Author

In this case plugin or kupfer must define this filter?

@bluss
Copy link
Member

bluss commented Apr 26, 2017

In this case the plugin itself defined that filter, so there was no/not so much resilience in that sense.

@KarolBedkowski
Copy link
Contributor

Closing due inactivity.

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

3 participants