From: Martijn Dekker <martijn@inlv.org>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: [BUG] 'cd -P' leaves double slash in $PWD
Date: Sat, 1 Feb 2020 03:15:31 +0100 [thread overview]
Message-ID: <963eb2c3-e6e6-15e9-9c3a-964b49c6b2c0@inlv.org> (raw)
$ zsh -c 'cd -P ////dev//; echo $PWD'
//dev
Expected output: /dev
A double initial slash in a canonicalised/normalised path is okay if the
original started with a double slash (as this could signify a Cygwin UNC
network path), but not if it started with one or more than two slashes.
Bug confirmed on zsh from current back to 5.0.8 (I didn't test earlier
versions).
--
modernish -- harness the shell
https://github.com/modernish/modernish
next reply other threads:[~2020-02-01 2:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 2:15 Martijn Dekker [this message]
2020-02-01 4:23 ` Daniel Shahaf
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=963eb2c3-e6e6-15e9-9c3a-964b49c6b2c0@inlv.org \
--to=martijn@inlv.org \
--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).