mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
[Feature Request] When downloading choose not to create a new folder #3838
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#3838
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 @godbgood on GitHub (Jan 25, 2016).
Something similar to some versions of uTorrent, (honestly can't find it anymore,) where you could choose to not create a new folder to put the .torrent contents in.
For example: When using qBT, some torrents that have multiple items bundled together qBT will automatically create a folder to put them in, even if I only want one of the items. In my case it's tv shows that come with little "thanks for downloading" .txt files. So an option to just stick the contents directly into the desired download path would be wonderful.
I use the uTorrent (used to) and qBT as a file sorter so I don't have to go through all my folders later, but making the extra folder is not helpful when I'll cut and paste out the one file.
Thanks!
@sledgehammer999 commented on GitHub (Jan 26, 2016):
Duplicate of #588.