Path: csiph.com!weretis.net!feeder6.news.weretis.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!bloom-beacon.mit.edu!171.64.64.130.MISMATCH!usenet.stanford.edu!not-for-mail
From: don fong <dfong@dfong.com>
Newsgroups: gnu.bash.bug
Subject: Re: misleading error message from variable modifier
Date: Thu, 1 Mar 2018 09:24:29 -0800
Lines: 26
Sender: dfong@dfong.org
Approved: bug-bash@gnu.org
Message-ID: <mailman.9958.1519925075.27995.bug-bash@gnu.org>
References: <CAHQakpWxVECCU_LgGmGFXo7_Pftm0rw4Cn8xoZbSqnTOdCZgUQ@mail.gmail.com> <268f06ff-55ee-4364-fa75-54081dc7869a@case.edu>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Cc: "bash.bug list" <bug-bash@gnu.org>
To: Chester Ramey <chet.ramey@case.edu>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <268f06ff-55ee-4364-fa75-54081dc7869a@case.edu>
Precedence: list
Xref: csiph.com gnu.bash.bug:13784

any feedback on this patch?

On Sat, Feb 24, 2018 at 11:24 AM, Chet Ramey <chet.ramey@case.edu> wrote:

> On 2/23/18 10:20 PM, don fong wrote:
> > hi folks.  i'm a bash user, who just noticed a slight anomaly.  it has
> > to with the shell variable modifier ${parameter?} .  according to the
> > man page, ${X?} should yield an error message and exit if X is unset,
> > otherwise the value of X.  in this case,
> >
> >     unset X; echo ${X?}
> >
> > i expect to get an error message, and indeed an error message results.
> >
> >     bash: X: parameter null or not set
> >
> > but i think the error message is misleading.
>
> Thanks for the report and patch. I'll take a look.
>
> Chet
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>                  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/
>