mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
no special characters in labels makes "append label to path" pretty pointless #1042
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#1042
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 @anohren on GitHub (Jan 2, 2014).
Like the title suggests, if I can't specify a path as a label (like "video\movie") then why would I want to append the label to the torrent's save path?
@sledgehammer999 commented on GitHub (Jan 2, 2014):
This isn't a bug. It is by design. For some insight see these relevant issues: #13 #917 #1090
@anohren commented on GitHub (Jan 3, 2014):
Thanks for the reply. If not here, where do I post about design issues?
I read the relevant issues but they seem to deal with multiple labels. I didn't really see what that had to do with special characters or specifying a path as a label. I for one couldn't be less interested in having multiple labels right now — I just want to specify a different path per label, and if I have to use the label name itself to do that then so be it. Although a separate field for relative or absolute path per label sounds more clean and multi-platform friendly.