Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Lack of sanitisation of I/O in pushd/popd

X-seq: zsh-workers 42375
From: Leah Neukirchen <leah@xxxxxxxx>
To: zsh-workers@xxxxxxx
Subject: Re: Lack of sanitisation of I/O in pushd/popd
Date: Mon, 19 Feb 2018 18:13:21 +0100
In-reply-to: <CAOr4F+P5ZVv4OiiodBkY2m3bxfNFTvX3ow2AUbuYxfU9CPYgUQ@mail.gmail.com> (Joao Paulo's message of "Mon, 19 Feb 2018 16:34:32 +0000")
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
References: <CAOr4F+P5ZVv4OiiodBkY2m3bxfNFTvX3ow2AUbuYxfU9CPYgUQ@mail.gmail.com>

Joao Paulo <joaolrpaulo@xxxxxxxxx> writes:

> Hello,
>
> I am encountering some problems with the implementation of the pushd and
> popd. The spaces in directory paths should be sanitise so I can read them
> properly. This is if I have a folder named Google Drive in my home
> directory, I expect it to be `~/Google\ Drive` not `~/Google Drive`, this
> is causing me problems to read the data from the `popd -n` because there is
> no difference between that whitespace, and the whitespace used to print
> elements in the stack.

popd -n is not even documented, and more a sideeffect of the
implementation that it works.

You can list the stack with "dirs -p" linewise, or just access the
array $dirstack directly.

hth,
-- 
Leah Neukirchen  <leah@xxxxxxxx>  http://leah.zone

References:
- Lack of sanitisation of I/O in pushd/popd
  - From: Joao Paulo

Messages sorted by: Reverse Date, Date, Thread, Author