Page 1 of 1
support for long directory-names
Posted: Sun Mar 07, 2010 11:37 pm
Usng Newsleechers smart-leech-feature gives me very long path-names, often longer than the allowed 255 chars. When that happens, NL puts the files into the main-download-directory, that can end up a bit messy.
But with NTFS we could use more space, up to 32767 chars (with up to 255 chars per componet).
Please support that in NL (maybe as nerdy option).
Posted: Wed Mar 17, 2010 3:46 pm
windows explorer wont read anything over 255 characters so whats the point of adding it ? yes i know you can use 3rd party programs to read it but how much of the userbase does?
Posted: Thu Mar 25, 2010 5:28 am
I am having a similiar problem with header names that are likely more than 256 characters. I haven't counted but someone went nuts patting themselves on the back and promoting then you get to the actual content description. When NL tries to act on these it tosses up an error message about the temp file directory full and has this 3 or 4 line file name. I can't find a way to get around it. Granted the poster should be givin the stink eye for posting the whole string in the file name, but even if it truncated the name or offered some sort of rename that would be better than just nothing. Just need a way to rename that header once it hits the que. Then we would be off to the races.
Posted: Thu May 27, 2010 3:31 pm
sheepshagger wrote:windows explorer wont read anything over 255 characters so whats the point of adding it ? yes i know you can use 3rd party programs to read it but how much of the userbase does?
I am aware of the limitations on file names in Win32. I don't think that exists in Win64 (though I have not tried to put 255 characters in a file name and I don't know why anyone would.) A lot of us have been running 64 bits for a long time. Even so, I don't think the file names are 255 characters, only the description in the groups (binary file groups.)
What would be the use of someone posting a file that no one would be able to acquire? Something seems very wrong about that and I don't believe that thousands of posters would do that knowing there posts were a total waste of effort. At least using Newsleecher, they are a total waste of effort and it would seem to me that Newsleecher is where the blame should fall. If that is truly a limitation of Newsleecher alone (the whole point of this post), then finding another tool is the only solution to this problem. So my inquiry is too find out if the above issue I have is a problem native only to Newsleecher or not. I have not performed any comparisons and I was hoping someone here had or had an answer on how to get Newsleecher to accept these files. I don't remember Newsleecher having these problems in much earlier versions. Surely Spiril has some insight into this as a programmer.
Thanks in advance for any help,