[Bug 233585] sh(1) ${param?} default error message is broken
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Nov 28 20:04:09 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233585
--- Comment #1 from commit-hook at 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 error
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
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-bugs
mailing list