News for hackers. Stuff that matters.

A comment on Why Does Windows Really Use Backslash as Path Separator?. Parent comment

Re:Why Does Windows Really Use Backslash as Path Separator? by userbinator on Friday May 24, 2019 @11:31PM (#20006945)
I'd say that's a bit of an edge case. Consider editing a file named README, index.html, .htaccess, or any number of other files which occur in many places with the same name.
[ Parent | on HN ]
Re:Why Does Windows Really Use Backslash as Path Separator? by a1369209993 on Saturday May 25, 2019 @05:48AM (#20008045)
Actually, that could still work:

  > in<TAB>
  index.html@.
  init.sh@..
  index.html@foobar@..
  ...
  inputrc@etc@/
The problem I see is this makes it hard to have domain-specific or optional address interpretation. Eg "[email protected][http]" or... something to that effect.
[ Parent | on HN ]
Re:Why Does Windows Really Use Backslash as Path Separator? by a1369209993 on Monday May 27, 2019 @09:54PM (#20026584)
> The problem I see

Come to think of it, that also breaks option escaping in glob et al:

  ./--kill=everything
  vs
  --kill=everything@.
[ Parent | on HN ]