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
What to do about . and .. in the middle of path abbreviation? With .. in paths the results would be too unpredictable. Are there any situations when .. show up in path? The user probably wouldn't type it but a command line tool could return such path.
I see double dots in filenames all the time when users create files on Windows where filename extensions are hidden by default. For example, when dealing with personal names: Truman, Harry S..pdf, Truman, H.S..pdf - Windows users just never see the .pdf at the end so no double-dots for them :)
The text was updated successfully, but these errors were encountered:
Thanks for the issue. Fortunately there is no problem with that case. By . and .. I meant path components 'current dir' and 'parent dir'. For now users can only put . and .. in the beginning of the path, like so:
kn ./../siblingfolder
However, I'm not sure whether kn should allow for abbreviations with the .. component in the middle i.e. foo/bar/../baz. Such abbreviation would cause kn to search for dir matching baz, which has a sibling matching bar, both in dir matching foo. If bar was a symlink, that would be even more complicated.
EDIT: Closing, since there are no problems with this case.
I see double dots in filenames all the time when users create files on Windows where filename extensions are hidden by default. For example, when dealing with personal names:
Truman, Harry S..pdf
,Truman, H.S..pdf
- Windows users just never see the.pdf
at the end so no double-dots for them :)The text was updated successfully, but these errors were encountered: