[Bug 233585] sh(1) ${param?} default error message is broken
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Dec 9 19:14:39 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233585
--- Comment #2 from commit-hook at freebsd.org ---
A commit references this bug:
Author: jilles
Date: Sun Dec 9 19:14:22 UTC 2018
New revision: 341767
URL: https://svnweb.freebsd.org/changeset/base/341767
Log:
MFC r341164: 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 error
message like
sh: param: parameter not set
This was broken by r316417.
PR: 233585
Changes:
_U stable/12/
stable/12/bin/sh/expand.c
stable/12/bin/sh/tests/expansion/Makefile
stable/12/bin/sh/tests/expansion/question2.0
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-bugs
mailing list