But from what I’ve read, Everything’s insane speed depends on file-metadata tables that are specific to NTFS and not present in … many? most? all? … Linux filesystems, so I’m guessing FSearch has to build its *own* extensive file-metadata tables and keep them updated in real time. I gather there is now an Everything-inspired search utility for Linux that’s in late beta, called FSearch.
It has officially become the Windows-only program I miss the *most* in Linux.
Additionally, because legacy 32-bit Windows programs and utilities may have been designed with the older 255-character (?) pathname limit in mind, path:len:>255 *might* be a safer bet, if compatibility with legacy 32-bit programs/utilities is what you’re checking for.įinally, Voidtools’ Everything search utility is indeed *awesome*. Also, 260 being the maximum “MAX_PATH” length, not the shortest “illegal” path length, I think >260 (not 259) is in fact correct. If you want to find *pathnames*, the syntax is path:len:>260. Regarding Everything, len:>260 just finds *filenames* (exclusive of path) that are over 260 characters in length. I don’t remember whether LongPathsEnabled was enabled by default in Windor whether I changed it, but it’s enabled. I think I’ve used some tricks from the command line a couple times, as well.Ĭurrently, I see that have LongPathsEnabled enabled in my registry, and I don’t think I run any legacy programs that weren’t designed to support long paths, so it’s not really an issue. I’m pretty sure I used a utility called something like “too long path detector” at some point in the past, and I *think* the way I deleted, moved, or renamed too-long-pathname files was to rename folders higher up the path with shorter names. These problems haven’t happened often enough for me to remember how I dealt with them. (I’m still not entirely clear on how a properly designed filesystem can allow a file with a filename or pathname that’s “too long to be deleted” to be created in the first place … but I’m just a user, not a filesystem designer.)
I’ve run into this problem a number of times, usually because I downloaded a file with a really long original filename without bothering to edit it down, into a folder with a longish path, subsequently edited the file, and then had an automatic syncing routine generate a versioned backup of the original file with a timestamp appended to it … often in a folder with an even *longer* path than the original file’s.
0 kommentar(er)
