zsh-users
 help / color / mirror / code / Atom feed
From: Phil Pennock <phil.pennock@globnix.org>
To: zsh-users@sunsite.dk
Subject: Re: Useful zsh/datetime things
Date: Fri, 10 Oct 2003 12:42:19 +0000	[thread overview]
Message-ID: <20031010124218.GA15016@globnix.org> (raw)
In-Reply-To: <1031010044052.ZM11468@candle.brasslantern.com>

On 2003-10-10 at 04:40 +0000, Bart Schaefer wrote:
> Because an unquoted empty string always disappears.  It just happens that
> the easiest way to get an unquoted empty string is to expand an unset or
> empty-valued parameter (the former assuming setopt no_unset).
> 
> "Not split" (in the sh_word_split sense) is not equivalent to "quoted".

Ah.  Good thing that long habit keeps me using "$@" instead of dropping
the quotes to get $@ for zsh then.

Any other side-effects to not quoting variables in zsh?  Backslash
degree-of-toothpickiness, I suppose.

> You'd get strange effects if it didn't work this way; e.g., $* would
> always substitute an empty string, even when $# == 0.

And you could of course get an empty string by explicitly using "$*" or
"${*:-}" which would be the same, but make the intention explicit.  Ta.
-- 
2001: Blogging invented. Promises to change the way people bore strangers with
banal anecdotes about their pets. <http://www.thelemon.net/issues/timeline.php>


  reply	other threads:[~2003-10-10 12:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09 17:27 Bart Schaefer
2003-10-09 17:49 ` Phil Pennock
2003-10-10  4:40   ` Bart Schaefer
2003-10-10 12:42     ` Phil Pennock [this message]
2003-10-09 18:04 ` Peter Stephenson
2003-10-09 18:12   ` Phil Pennock
2003-10-10  2:15     ` Bart Schaefer
2003-10-10 12:56       ` Phil Pennock
2003-10-10 16:46         ` Dan Nelson
2003-10-09 21:29 ` Oliver Kiddle
2003-10-10  2:12   ` Bart Schaefer
2003-10-10  9:30   ` Peter Stephenson
2003-10-22 15:31 ` Bart Schaefer

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=20031010124218.GA15016@globnix.org \
    --to=phil.pennock@globnix.org \
    --cc=zsh-users@sunsite.dk \
    /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).