From: Mikael Magnusson <mikachu@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: string to array space problem in filenames
Date: Fri, 28 Aug 2015 05:15:16 +0200 [thread overview]
Message-ID: <CAHYJk3TNvPnByF7m4Pa=DB1Qyu5L6svnLS-uiZ5sqpfbti_-mQ@mail.gmail.com> (raw)
In-Reply-To: <55DFC1E6.5090400@eastlink.ca>
On Fri, Aug 28, 2015 at 4:05 AM, Ray Andrews <rayandrews@eastlink.ca> wrote:
> Gentlemen:
>
> I should probably know this, but I'm rusty after a few months not thinking
> about zsh. I have a personal implementation of a dirstack that just pushes
> $PWD to the end of a file then rereads the file to an array which is then
> sent to 'select' to let me change directory. I like it because it survives
> reboot and works across xterms and removes duplicates and so on. The only
> thing that trips it up is when a directory is pushed that contains a space.
> I have few of those, so it's just an irritation, still I'd like to fix it if
> possible. Here's one of the offending directories:
>
> pts/1 HP-w5--5-Debian1 root /root/.icedove/Ray/Mail/Local Folders
>
> ... which 'select' does this with:
>
>
> 1) QUIT
> 2) /aWorking/Zsh
> 3) Folders
> 4) /root/.icedove/Ray/Mail/Local
>
> ... because it breaks at the space, obviously. Is there some way around
> that? I've tried various quotes and slashes and incantations and spells,
> but no luck. I expect that 'select' can't be expected to behave differently
> so somehow the array needs to know to protect spaces in directory names.
> I'm fuzzified why protecting them with quotes doesn't do it.
You forgot to include your code in the mail.
--
Mikael Magnusson
next prev parent reply other threads:[~2015-08-28 3:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 20:50 zsh 5.0.8-test-2 Peter Stephenson
2015-08-22 0:10 ` Matthew Martin
2015-08-22 0:30 ` Michael Beasley
2015-08-22 0:45 ` Matthew Martin
2015-08-22 11:48 ` Jun T.
2015-08-22 17:04 ` Matthew Martin
2015-08-23 8:31 ` Daniel Shahaf
2015-08-23 12:45 ` Jun T.
2015-08-28 2:05 ` string to array space problem in filenames Ray Andrews
2015-08-28 3:15 ` Mikael Magnusson [this message]
2015-08-28 18:54 ` Ray Andrews
2015-08-28 19:43 ` Bart Schaefer
2015-08-28 20:42 ` Ray Andrews
2015-08-28 20:56 ` Peter Stephenson
2015-09-03 3:37 ` Ray Andrews
2015-09-03 4:48 ` Kurtis Rader
2015-09-03 5:25 ` Bart Schaefer
2015-09-03 5:53 ` Mikael Magnusson
2015-09-03 15:23 ` Ray Andrews
2015-09-03 15:30 ` Mikael Magnusson
2015-09-03 15:58 ` Ray Andrews
2015-09-03 16:08 ` Peter Stephenson
2015-09-03 16:11 ` Ray Andrews
2015-09-03 17:11 ` Ray Andrews
[not found] ` <55E86E0C.1000806__15798.3473306105$1441295967$gmane$org@eastlink.ca>
2015-09-03 16:21 ` Stephane Chazelas
2015-08-28 9:40 ` Peter Stephenson
2015-08-28 19:02 ` Ray Andrews
2015-08-28 19:45 ` Bart Schaefer
2015-08-28 20:35 ` Ray Andrews
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='CAHYJk3TNvPnByF7m4Pa=DB1Qyu5L6svnLS-uiZ5sqpfbti_-mQ@mail.gmail.com' \
--to=mikachu@gmail.com \
--cc=rayandrews@eastlink.ca \
--cc=zsh-users@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).