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
I've been using these to try to normalize odd user path entries, ei (\\programdata or c:\\programdata would both change to c:\\programdata on all windows systems)
But the issue fields are root and dir. Dir contains root, but wouldn't it make sense for it to omit root?
Furthermore this doesn't work, probably a result of the ambiguity in ^:
path.format is behaving as expected here because the root value should always be the same as the start of the dir value. It makes sense for dir to contain the root because you want dir to be the absolute path to the directory of the path being parsed. dir without the root would be a pretty useless value in most cases (perhaps not in your case, but for the majority of users).
I think the solution outlined in #1999 would be helpful in solving your problem, but as I suggested there, it's probably best suited for user-land.
I've been using these to try to normalize odd user path entries, ei (
\\programdata
orc:\\programdata
would both change toc:\\programdata
on all windows systems)Similar issue as this: #1999
But the issue fields are
root
anddir
. Dir contains root, but wouldn't it make sense for it to omit root?Furthermore this doesn't work, probably a result of the ambiguity in ^:
output:
The text was updated successfully, but these errors were encountered: