5 ms·

Except those are completely different paths on the two systems (even if the path separator was the same).

deleted 4y ago
[deleted]
Shared404 4y ago
And it's ok to use the default seperator for whichever OS you're using. It's gonna be a different path anyways when you're talking about windows, may as well use the right syntax.
- pwdisswordfish9 4y ago
  This thinking of backslash as being "the right syntax" for Windows paths is pretty much the reason why the earlier comment was posted.
  - jjnoakes 4y ago
    I don't follow. Add far as I know, backslash is the "right" path separator on Windows - it works everywhere, is the documented canonical path separator, and has the fewest compatibility issues with programs. And even if it was on equal footing with forward slash on Windows (which it isn't), bringing it up as an alternative just seemed off-topic.
xxs 4y ago
point is - it has been possible to use the forward slash in windows for over 20y... except in some UIs that insist that it has to be backslash.
- jjnoakes 4y ago
  Point is, why bring up the non-default alternative path separator that doesn't work universally in Windows when the original comment was correct as is?
pwdisswordfish9 4y ago
Uh... "Except"? What does that observation have to do with anything? It was a gentle reminder that reaching for backslash is not necessary. Nowhere does it say "you can paste the same absolute path in on any system, without regard for where the files actually live".
- jjnoakes 4y ago
  > What does that observation have to do with anything? About as much as the comment I replied to did, I suppose. Since the paths were right as originally written, and since changing from backslash to forward slash doesn't remove the need to list both paths anyway, bringing up the other ways of writing the windows path seemed unnecessary. But I was feeling charitable and thought that perhaps you read the original comment too quickly and assumed that the paths were the same except for the slash direction, which would give your comment a little more purpose, and which also gives my reply a little purpose as well. If that wasn't the case then neither post has any purpose.
  - pwdisswordfish9 4y ago
    > But I was feeling charitable Making assumptions about the other person that set you up to argue against whatever position that entails is not what it means to be charitable. It is the opposite. It is uncharitable. (At least to the other person; it's charitable, perhaps, to you.) > neither post has any purpose Wrong. It has the same purpose now as it did from the beginning—reminding/alerting people to the fact that using backslashes in paths just because you're talking about Windows is not necessary.
    - jjnoakes 4y ago
      Using one of the correct path separators for the OS isn't necessary? And someone using one of the correct path separators needs a reminder that other path separtors exist? There was no more purpose to that than reminding someone that they could have used UNC paths, URIs, 8.3 short names, ...

deleted 4y ago

[deleted]

And it's ok to use the default seperator for whichever OS you're using. It's gonna be a different path anyways when you're talking about windows, may as well use the right syntax.

pwdisswordfish9 4y ago
This thinking of backslash as being "the right syntax" for Windows paths is pretty much the reason why the earlier comment was posted.
- jjnoakes 4y ago
  I don't follow. Add far as I know, backslash is the "right" path separator on Windows - it works everywhere, is the documented canonical path separator, and has the fewest compatibility issues with programs. And even if it was on equal footing with forward slash on Windows (which it isn't), bringing it up as an alternative just seemed off-topic.

xxs 4y ago

point is - it has been possible to use the forward slash in windows for over 20y... except in some UIs that insist that it has to be backslash.

jjnoakes 4y ago
Point is, why bring up the non-default alternative path separator that doesn't work universally in Windows when the original comment was correct as is?

pwdisswordfish9 4y ago

Uh... "Except"? What does that observation have to do with anything? It was a gentle reminder that reaching for backslash is not necessary. Nowhere does it say "you can paste the same absolute path in on any system, without regard for where the files actually live".

jjnoakes 4y ago
> What does that observation have to do with anything? About as much as the comment I replied to did, I suppose. Since the paths were right as originally written, and since changing from backslash to forward slash doesn't remove the need to list both paths anyway, bringing up the other ways of writing the windows path seemed unnecessary. But I was feeling charitable and thought that perhaps you read the original comment too quickly and assumed that the paths were the same except for the slash direction, which would give your comment a little more purpose, and which also gives my reply a little purpose as well. If that wasn't the case then neither post has any purpose.
- pwdisswordfish9 4y ago
  > But I was feeling charitable Making assumptions about the other person that set you up to argue against whatever position that entails is not what it means to be charitable. It is the opposite. It is uncharitable. (At least to the other person; it's charitable, perhaps, to you.) > neither post has any purpose Wrong. It has the same purpose now as it did from the beginning—reminding/alerting people to the fact that using backslashes in paths just because you're talking about Windows is not necessary.
  - jjnoakes 4y ago
    Using one of the correct path separators for the OS isn't necessary? And someone using one of the correct path separators needs a reminder that other path separtors exist? There was no more purpose to that than reminding someone that they could have used UNC paths, URIs, 8.3 short names, ...