From: "Dian M Fay" <dian.m.fay@gmail.com>
To: "Roman Perepelitsa" <roman.perepelitsa@gmail.com>
Cc: "Zsh hackers list" <zsh-workers@zsh.org>
Subject: Re: [PATCH] expand '..n' to equivalent number of '..' segments in fixdir
Date: Sun, 10 May 2020 01:28:27 -0400 [thread overview]
Message-ID: <C2MSV2HLF6WI.3SYUHVURJH6TE@lamia> (raw)
In-Reply-To: <CAN=4vMr_8j03P2oY0+9SLgBnMWMtGtrnUag7fte =18VnvUtRKg@mail.gmail.com>
Of course. Actually encountering a directory named like that does seem
unlikely, but unlikely probably doesn't cut it. It could stat beforehand
but then the ..n behavior becomes less consistent.
Would making this an option ('BACKTRACK_N' or something) be appropriate?
On Sun May 10, 2020 at 6:43 AM, Roman Perepelitsa wrote:
> On Sun, May 10, 2020 at 6:36 AM Dian M Fay <dian.m.fay@gmail.com> wrote:
> >
> > dian@lamia ~/work/zsh cd ..2
> > dian@lamia ~ cd ..123
> > dian@lamia /
>
>
> `..2` is a valid directory name. So it's a breaking change.
>
>
> ~% mkdir ..2
> ~% cd ..2
> ~/..2%
>
>
> Roman.
next parent reply other threads:[~2020-05-10 5:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAN=4vMr_8j03P2oY0+9SLgBnMWMtGtrnUag7fte =18VnvUtRKg@mail.gmail.com>
2020-05-10 5:28 ` Dian M Fay [this message]
2020-05-10 7:06 ` Eric Cook
2020-05-10 7:09 ` Eric Cook
2020-05-10 14:21 ` Daniel Shahaf
2020-05-10 4:37 Dian M Fay
2020-05-10 4:43 ` Roman Perepelitsa
2020-05-10 5:58 ` Bart Schaefer
2020-05-10 6:28 ` Bart Schaefer
2020-05-10 17:17 ` Dian M Fay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C2MSV2HLF6WI.3SYUHVURJH6TE@lamia \
--to=dian.m.fay@gmail.com \
--cc=roman.perepelitsa@gmail.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).