zsh-workers
 help / color / mirror / code / Atom feed
From: "Nikolay Aleksandrovich Pavlov (ZyX)" <kp-pav@yandex.ru>
To: Ronald Fischer <ynnor@mm.st>,
	Peter Stephenson <p.stephenson@samsung.com>,
	"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Bug in parameter expansion with :-    ?
Date: Tue, 10 Jan 2017 21:41:58 +0300	[thread overview]
Message-ID: <3499521484073718@web13o.yandex.ru> (raw)
In-Reply-To: <1484063743.4187904.843219497.103F256C@webmail.messagingengine.com>



10.01.2017, 18:56, "Ronald Fischer" <ynnor@mm.st>:
> On Tue, Jan 10, 2017, at 16:43, Peter Stephenson wrote:
>>  On Tue, 10 Jan 2017 16:35:00 +0100
>>  Ronald Fischer <ynnor@mm.st> wrote:
>>
>>  > This expands correctly to a '+':
>>  >
>>  > ${unset_variable:-+}
>>  >
>>  > This however doesn't expand to a '-', but to the empty string:
>>  >
>>  > ${unset_variable:--}
>>
>>  You may be getting into confusions with options to builtins rather than
>>  the expansion.
>>
>>  % print -r -- ${unset_variable:--}
>>  -
>
> Yes I do! You are right - not a bug!
>
> Ronald

For checking what argument is literally I would suggest `printf '<%s>' $arg` instead: this will show trailing spaces due to `<>` around `%s`, let you distinguish between variable accidentally becoming an array and determine which strings are in one array item exactly (`printf '<%s>' 1 2` results in `<1><2>`, harder to miss then a space). And this also does not look like you are fighting with zsh (`-r` and `--` are there to prevent some misinterpretations).


      reply	other threads:[~2017-01-10 18:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170110153530epcas3p444d88e1dff85a69371df2472330b006b@epcas3p4.samsung.com>
2017-01-10 15:35 ` Ronald Fischer
2017-01-10 15:43   ` Peter Stephenson
2017-01-10 15:55     ` Ronald Fischer
2017-01-10 18:41       ` Nikolay Aleksandrovich Pavlov (ZyX) [this message]

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=3499521484073718@web13o.yandex.ru \
    --to=kp-pav@yandex.ru \
    --cc=p.stephenson@samsung.com \
    --cc=ynnor@mm.st \
    --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).