You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While using the go-ipfs cli on a windows git-bash terminal, I'm running into an issue where the ipfs files commands are escaping forward slashes: /:
Fails:
$ ipfs files mkdir /breakfast
Error: Paths must start with a leading slash.
Works:
$ ipfs files mkdir //breakfast
I have this general problem with all ipfs files commands. Looked around through some issues and this one could be related to another recent issue #4602 but you guys would know more.
The text was updated successfully, but these errors were encountered:
This is actually an issue with git-bash and I'm not sure there's much we can do about it. Unfortunately, git-bash recognizes that ipfs is a windows command, sees that /breakfast is a path, and then rewrites it as a windows path (probably as something like C:\path\to\git\bash\root\breakfast).
Apparently, setting MSYS_NO_PATHCONV=1 may fix this (git bash uses msys). Alternatively, passing a double leading slash will tell git bash to not rewrite the path.
Version information:
Type: bug
Severity: High?
Description:
While using the go-ipfs cli on a windows git-bash terminal, I'm running into an issue where the
ipfs files
commands are escaping forward slashes:/
:Fails:
Works:
I have this general problem with all
ipfs files
commands. Looked around through some issues and this one could be related to another recent issue #4602 but you guys would know more.The text was updated successfully, but these errors were encountered: