no path join, or separator? about fs HOT 8 CLOSED

(fs/file "a" "path" "segment")

from fs.

💣 boom.

from fs.

Lets 🐛 @amalloy all right now 👯 💃 👯

from fs.

fs/file is not just doing a join. It's also doing cwd operations. I guess I can use io/file.

from fs.

Why does that matter? It'll have the same effect as io/file if cwd hasn't changed.

On Wed, Sep 18, 2013 at 1:16 PM, acthp [email protected] wrote:

fs/file is not just doing a join. It's also doing cwd operations. I guess I can use io/file.

Reply to this email directly or view it on GitHub:
#59 (comment)

from fs.

No, that's incorrect.

cavm.cgdata=> (fs/file "one")
#<File /inside/home/craft/cavm/one>
cavm.cgdata=> (io/file "one")
#<File one>

from fs.

All it did was make the path absolute to the current working directory which is what would happen later when you need to actually do an operation or something, but fair enough. In any case, io/file and fs/file are the things one is meant to use to do what you want to do.

As for the separator bit, if it isn't exposed I'd take a pull request to add it.

from fs.

It matters when working with abstract paths, for example when dealing with files that contain references to other files. I'm doing transforms on such files, not actually reading the files they point to. So if there's a relative reference like "../over/there", and it gets changed to an absolute reference on the filesystem, the file is now broken.

It's important to be able to normalize paths while doing this, however normalize-path also converts them to absolute references. More worrying, it looks like the underlying java call .getCanonicalFile also does this. I can work around it by prepending root, then removing it. Kinda clumsy.

from fs.