Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [patch] Fix VCS_INFO_reposub's whitespace handling
- X-seq: zsh-workers 33267
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: [patch] Fix VCS_INFO_reposub's whitespace handling
- Date: Sun, 28 Sep 2014 11:52:43 -0700
- Cc: Marco Hinz <mh.codebro@xxxxxxxxx>
- In-reply-to: <20140928171033.GA11234@cheyenne>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20140928171033.GA11234@cheyenne>
On Sep 28, 7:10pm, Marco Hinz wrote:
}
} I'm new to zsh internals, but apparently something causes the string
} 'foo bar' to be read in as 2 arguments. printf only takes 1
} argument, and so 'bar' just gets appended.
}
} Could someone point me to the appropriate parameter expansion rule?
}
} Solution:
}
} Double-quote ${$(pwd -P)#$base/}.
It's the $(pwd -P) that's the problem; $(...) is subject to $IFS split
unless quoted. Section 14.4 "Command Substitution" in the docs.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author