Author tuxtimo
Recipients brett.cannon, pitrou, serhiy.storchaka, steve.dower, tuxtimo, yselivanov
Date 2018-06-02.10:45:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527936338.75.0.592728768989.issue33739@psf.upfronthosting.co.za>
In-reply-to
Content
> I've just tried, "..." doesn't seem to mean anything on the Windows CLI.

It's not only about Windows / Linux here - it's about the shell and command which is being used. If we talk about "cd" for example - it's a builtin in most common shells on Linux, which behave differently:

bash:

    /a/b/c $ cd ...
    bash: cd: ...: No such file or directory

dash:

    /a/b/c $ cd ...
    dash: 8: cd: can't cd to ...

zsh:

    /a/b/c $ cd ...
    /a $

I think using '...' to navigate to the parent is confusing. 
It's well known and agreed that '..' is for navigating to the parent. 
'...' looks similar but is definitely not the same as '..' and therefore shouldn't be treated as such.
History
Date User Action Args
2018-06-02 10:45:38tuxtimosetrecipients: + tuxtimo, brett.cannon, pitrou, serhiy.storchaka, yselivanov, steve.dower
2018-06-02 10:45:38tuxtimosetmessageid: <1527936338.75.0.592728768989.issue33739@psf.upfronthosting.co.za>
2018-06-02 10:45:38tuxtimolinkissue33739 messages
2018-06-02 10:45:38tuxtimocreate