starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Editing search results #11996

New issue

Open

opened 2026-02-21 22:12:22 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-21 22:12:22 -05:00

Owner

Originally created by @vertap on GitHub (Apr 9, 2021).

Please provide the following information

qBittorrent version and Operating System

v4.3.3 (windows 10)

If on linux, libtorrent-rasterbar and Qt version

(type here)

What is the problem

Sometimes there are too many results even after using filter, but I can't remove the unwanted lines.

What is the expected behavior

I want to have some ways to remove unwanted result lines in search results.
In the "Filter search results..." editbox, I want to use minus signs before words that i don't want (-someword) like in google.
In the "Filter search results..." editbox, I want to use multiple filtering words.
Thank you all ~~~

Steps to reproduce

(type here)

Extra info(if any)

(type here)

Originally created by @vertap on GitHub (Apr 9, 2021). **Please provide the following information** ### qBittorrent version and Operating System v4.3.3 (windows 10) ### If on linux, libtorrent-rasterbar and Qt version (type here) ### What is the problem Sometimes there are too many results even after using filter, but I can't remove the unwanted lines. ### What is the expected behavior 1. I want to have some ways to remove unwanted result lines in search results. 2. In the "Filter search results..." editbox, I want to use minus signs before words that i don't want (-someword) like in google. 3. In the "Filter search results..." editbox, I want to use multiple filtering words. Thank you all ~~~ ### Steps to reproduce (type here) ### Extra info(if any) (type here)

deekerman added the

Feature request

Search engine

labels

2026-02-21 22:12:22 -05:00

deekerman commented

2026-02-21 22:12:30 -05:00

Author

Owner

@slrslr commented on GitHub (Oct 21, 2022):

Yes, when qbt detects in Search filtering field " -something " it should exclude results containing "something". It would greatly improve search. I want to exclude multiple phrases sometimes:

include include2 -exclude -"exclude too" -'exclude also'

Another way, even less handy would be to allow turning filtering field into negative, meaning it will exclude what is typed into it.

Similar issues: #9251 #10241

@slrslr commented on GitHub (Oct 21, 2022): Yes, when qbt detects in Search filtering field " -something " it should exclude results containing "something". It would greatly improve search. I want to exclude multiple phrases sometimes: include include2 -exclude -"exclude too" -'exclude also' Another way, even less handy would be to allow turning filtering field into negative, meaning it will exclude what is typed into it. Similar issues: #9251 #10241

deekerman commented

2026-02-21 22:12:32 -05:00

Author

Owner

@veloute commented on GitHub (Mar 6, 2023):

Yes, when qbt detects in Search filtering field " -something " it should exclude results containing "something". It would greatly improve search. I want to exclude multiple phrases sometimes:

include include2 -exclude -"exclude too" -'exclude also'

Another way, even less handy would be to allow turning filtering field into negative, meaning it will exclude what is typed into it.

Similar issues: #9251 #10241

is this planned on being implemented?

@veloute commented on GitHub (Mar 6, 2023): > Yes, when qbt detects in Search filtering field " -something " it should exclude results containing "something". It would greatly improve search. I want to exclude multiple phrases sometimes: > > include include2 -exclude -"exclude too" -'exclude also' > > Another way, even less handy would be to allow turning filtering field into negative, meaning it will exclude what is typed into it. > > Similar issues: #9251 #10241 is this planned on being implemented?

deekerman commented

2026-02-21 22:12:32 -05:00

Author

Owner

@s38b35M5 commented on GitHub (Nov 10, 2023):

This was requested in #153

Also (and perhaps this is implemented and I did not realise it) it would be useful to be able to use logical operators in the search box, such as AND, OR, NOT, etc.

...but must have been overlooked.

Perhaps a better title @vertap that includes "Operators" or "Exclude" or similar would help

@s38b35M5 commented on GitHub (Nov 10, 2023): This was requested in #153 > Also (and perhaps this is implemented and I did not realise it) it would be useful to be able to use logical operators in the search box, such as AND, OR, NOT, etc. ...but must have been overlooked. Perhaps a better title @vertap that includes "Operators" or "Exclude" or similar would help

deekerman commented

2026-02-21 22:12:32 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 24, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 24, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**