git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Adeodato Simó" <dato@net.com.org.es>
To: "Boyd Stephen Smith Jr." <bss@iguanasuicide.net>
Cc: Ted Pavlic <ted@tedpavlic.com>, git@vger.kernel.org
Subject: Re: [PATCH] Update bash completions to prevent unbound variable errors.
Date: Mon, 12 Jan 2009 21:40:30 +0100	[thread overview]
Message-ID: <20090112204030.GA23327@chistera.yi.org> (raw)
In-Reply-To: <200901121435.35547.bss@iguanasuicide.net>

* Boyd Stephen Smith Jr. [Mon, 12 Jan 2009 14:35:35 -0600]:

> >The attached patch replaces things like

> >         if [ -z "$1" ]

> >with

> >         if [ -z "${1-}" ]

> That looks ugly to me.  Any reason we shouldn't just "set +u" at the top of 
> the script?

`set +u` affects the shell globally, not just to the sourced file. If
you do that, you must be aware that you'll be preventing people from
running their shell in `set -u` mode. (Merely stating a fact here, not
giving any opinion.)

-- 
Adeodato Simó                                     dato at net.com.org.es
Debian Developer                                  adeodato at debian.org
 
The problem I have with making an intelligent statement is that some
people then think that it's not an isolated occurrance.
                -- Simon Travaglia

  reply	other threads:[~2009-01-12 20:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 19:58 [PATCH] Update bash completions to prevent unbound variable errors Ted Pavlic
2009-01-12 20:35 ` Boyd Stephen Smith Jr.
2009-01-12 20:40   ` Adeodato Simó [this message]
2009-01-12 21:27     ` Boyd Stephen Smith Jr.
2009-01-12 21:31       ` Shawn O. Pearce
2009-01-12 21:38         ` Boyd Stephen Smith Jr.
2009-01-12 21:11   ` Ted Pavlic
2009-01-12 21:21     ` Ted Pavlic
2009-01-12 21:32       ` Shawn O. Pearce
2009-01-12 21:51         ` Ted Pavlic
2009-01-12 21:25     ` Adeodato Simó
2009-01-12 21:37       ` Ted Pavlic
2009-01-12 21:47         ` Adeodato Simó
2009-01-12 21:40 ` Adeodato Simó

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=20090112204030.GA23327@chistera.yi.org \
    --to=dato@net.com.org.es \
    --cc=bss@iguanasuicide.net \
    --cc=git@vger.kernel.org \
    --cc=ted@tedpavlic.com \
    /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.
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).