#4 Don't rebuild the path up to the source folder, but rebuild the folder structure within the source folder

[Alessander Botti Benevides]

Firstly, thank you very much for the very nice program! My feature request is an option slightly weaker than “Don't rebuild path?”. I would like to rebuild only the paths "within" the source folder, but not the full path up to the source folder. The reason is that the Linux kernel imposes a limit on the size of a path (PATH_MAX). So, if the target directory is already on a long path, rebuilding all the path up to the source folder within the target folder may reach this PATH_MAX limit. This problem frequently happens to me. Moreover, another reason is that the path up to the source folder is not useful to me, what is useful is just the folder structure within the source folder.

[TEDs TECH]

Firstly, thank you very much for the very nice program!

OK, thank you.

The reason is that the Linux kernel imposes a limit on the size of a path (PATH_MAX).

So too does the Windows OS, allbeit Windows is much smaller at just 260 characters for ANSI names. Linux, on the other hand, allows for 4K. If a folders length is greater than that, I consider that quite extreme?

That said, I am, just this very week, working on a Unicode call to the Windows API to bypass the Windows OS restrictions, given that NTFS allows up to 32K length.

The problem with long directory names also affects the ability of QuickHash to FIND the files in the first place. This is also something I am working on at the same time. In other words, QH will find all the files in a folder < Length(MAX_PATH), but not those that are nested in ones > Length(MAX_PATH). In Windows, this can be more common than I'd like. In Linux, I'd consider it quite rare, but I assume this is affecting you.

I will accept the ticket and add it to my list. Thanks for the information.