mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Select names of files 100% from incomplete download #16321
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#16321
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @G-e-V-e on GitHub (Nov 5, 2024).
Suggestion
Suppose you're downloading a folder containing 100 files. The last seed goes away (or there may not even be seeds, just peers) so you end up with an incomplete folder download with no hope to ever complete it. But if it's incomplete at a high percentage (such as 95%), it means up to 95 files in that downloaded folder may be at 100% while a minority of the files are useless.
Actually, there is NO WAY that I know of to select all file names in the Content view matching a given criterium (such as all files at less than 100% Progress to be able to delete these files from the containing folder).
Use case
Extra info/examples/attachments
No response
@xavier2k6 commented on GitHub (May 25, 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 ❤
reactionsin 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:
DO NOT:
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)
@G-e-V-e commented on GitHub (May 26, 2025):
Thanks for considering this feature request. If implemented, it would make saving precious files that would otherwise be lost a lot easier. Think of collections of ebooks or photos, for example.
Van: xavier2k6 @.>
Verzonden: zondag 25 mei 2025 16:21
Aan: qbittorrent/qBittorrent @.>
CC: G-e-V-e @.>; Author @.>
Onderwerp: Re: [qbittorrent/qBittorrent] Select names of files 100% from incomplete download (Issue #21779)
[https://avatars.githubusercontent.com/u/42386382?s=20&v=4]xavier2k6 left a comment (qbittorrent/qBittorrent#21779)https://github.com/qbittorrent/qBittorrent/issues/21779#issuecomment-2907854482
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:
DO NOT:
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)
—
Reply to this email directly, view it on GitHubhttps://github.com/qbittorrent/qBittorrent/issues/21779#issuecomment-2907854482, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIWRIP3ZP7XUH44G6KVYBCD3AHGXJAVCNFSM6AAAAABRGPSJHOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBXHA2TINBYGI.
You are receiving this because you authored the thread.Message ID: @.***>