starred/qBittorrent

Fork 0

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

List path when deleting files #1598

New issue

Open

opened 2026-02-21 15:44:51 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-21 15:44:51 -05:00

Owner

Originally created by @Meriipu on GitHub (Jul 27, 2014).

Listing the path(s) to the top directory when deleting files from disk in the case that it has been saved or moved to a non-default location.

So to avoid accidentally deleting a download you did not remember to copy (is making copies from the Downloads folder to say Music/ a normal thing to do?) -- listing the path reminds you

I usually copy, but it caught me once where my Download and Library location was the same

I realize this is obscure

Originally created by @Meriipu on GitHub (Jul 27, 2014). Listing the path(s) to the top directory when deleting files from disk in the case that it has been saved or moved to a non-default location. So to avoid accidentally deleting a download you did not remember to copy (is making copies from the Downloads folder to say Music/ a normal thing to do?) -- listing the path reminds you I usually copy, but it caught me once where my Download and Library location was the same I realize this is obscure

deekerman added the

Feature request

label

2026-02-21 15:44:51 -05:00

deekerman commented

2026-02-21 15:44:53 -05:00

Author

Owner

@chrishirst commented on GitHub (Jul 28, 2014):

BitTorrent clients do NOT use 'files' or 'folders' to identify the payload, so it does not 'know' the 'path'.

@chrishirst commented on GitHub (Jul 28, 2014): BitTorrent clients do NOT use 'files' or 'folders' to identify the payload, so it does not 'know' the 'path'.

deekerman commented

2026-02-21 15:44:55 -05:00

Author

Owner

@Meriipu commented on GitHub (Jul 28, 2014):

Does it not even know the location of the payload, disregarding the name of it (since you can select which directory to download to) ?

@Meriipu commented on GitHub (Jul 28, 2014): Does it not even know the location of the payload, disregarding the name of it (since you can select which directory to download to) ?

deekerman commented

2026-02-21 15:44:55 -05:00

Author

Owner

@chrishirst commented on GitHub (Jul 29, 2014):

Folders do not actually exist on the disc, they are just 'pointers' in a database for us stupid humans to look at. So when you "move" a file between folders, or rename a folder, or "move" a folder to be a subfolder, on the same drive (or filing system for Linux/Mac) you are NOT physically 'moving' anything, the DFS (disc filing system) is merely updating the human readable name that is associated with the physical clusters (a collection of magnetic domains) on the disc platter(s)

The pointer name is basically only used for "display purposes"

@chrishirst commented on GitHub (Jul 29, 2014): Folders do not actually exist on the disc, they are just 'pointers' in a database for us stupid humans to look at. So when you "move" a file between folders, or rename a folder, or "move" a folder to be a subfolder, on the same drive (or filing system for Linux/Mac) you are NOT physically 'moving' anything, the DFS (disc filing system) is merely updating the human readable name that is associated with the physical clusters (a collection of magnetic domains) on the disc platter(s) The pointer name is basically only used for "display purposes"

deekerman commented

2026-02-21 15:44:55 -05:00

Author

Owner

@Meriipu commented on GitHub (Jul 29, 2014):

hey now, I feel we are being unnecessarily pedantic here. Something has to request the operating system to make the directorypointer, is that something libtorrent/qbittorrent?

Could not that something ask the operating system whether that directorypointer already exists, and before requesting it to be made, ask the user whether to go ahead given that it already exists?

if this is a libtorrent thing then I can see why there is little point posting it here, butt if it is a qbittorrent thing then really now

@Meriipu commented on GitHub (Jul 29, 2014): hey now, I feel we are being unnecessarily pedantic here. Something has to request the operating system to make the directorypointer, is that something libtorrent/qbittorrent? Could not that something ask the operating system whether that directorypointer already exists, and before requesting it to be made, ask the user whether to go ahead given that it already exists? if this is a libtorrent thing then I can see why there is little point posting it here, butt if it is a qbittorrent thing then really now

deekerman commented

2026-02-21 15:44:55 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 23, 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 23, 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.)**