Date: Wed, 28 Nov 2018 20:04:03 +0000
From: bugzilla-noreply@freebsd.org
To: bugs@FreeBSD.org
Subject: [Bug 233585] sh(1) ${param?} default error message is broken
Message-ID: <bug-233585-227-NkopWmeteX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-233585-227@https.bugs.freebsd.org/bugzilla/>
References: <bug-233585-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233585 --- Comment #1 from commit-hook@freebsd.org --- A commit references this bug: Author: jilles Date: Wed Nov 28 20:03:54 UTC 2018 New revision: 341164 URL: https://svnweb.freebsd.org/changeset/base/341164 Log: sh: Fix ${param?} default error message If word in ${param?word} is missing, the shell shall write a default error message. So expanding ${param?} when param is not set should write an err= or message like sh: param: parameter not set This was broken by r316417. PR: 233585 Changes: head/bin/sh/expand.c head/bin/sh/tests/expansion/Makefile head/bin/sh/tests/expansion/question2.0 --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233585-227-NkopWmeteX>