4 ms·
You're assuming all paths are created and consumed by humans. Automated processes could easily generate and work with long paths for perfectly-valid reasons. A
by jsankey 13y ago
You're assuming all paths are created and consumed by humans. Automated processes could easily generate and work with long paths for perfectly-valid reasons. A limit this low causes grief for people that "deserve" better.
- lewispollard 13y agoExactly, recently had some visual studio build problems with a large repository and local node modules going over the file path limit.
- rcxdude 13y agoIndeed, I've even managed to run into this issue on linux, where an openembedded build would fail because the list of files passed to a command in a shell script would not fit in the buffer of arguments (about 5K IIRC). Fixing it would require recompiling the kernel.
- lifeisstillgood 13y agoBut that's surely an argument for rewriting the command or the shell script? Yes its freaking annoying, but I think having a path > 260 chars or a need to pass 5000+ bytes in as line arguments all count as "code smells". If you are hitting these issues, something else is wrong and in my experience, fixing the other things is much much more productive.