Re: Bug with unset variables

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

[Apparently when I tried to go look at another message, a blank reply
got sent off.]

On Fri, Nov 27, 2020 at 3:38 PM Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx> wrote:
>
> The best way to move forward would be to write a patch against the Test/
> directory that specifies the proposed behaviour.  Use the "f" flag so
> all newly-added tests will run, rather than just the first.

There are existing tests that specifically check for the current
behavior, so it's not as if this were simply overlooked.

To write the proposed new test cases, we need to decide (this list may
not be all-inclusive):

whether this is going to be attached to an option (and which one, now
that Oliver to at least some extent disagrees with KSH_TYPESET) or is
controlled by emulation mode;

what happens to "setopt NO_UNSET";

what "typeset -p" outputs following "unset".;

what happens when each (any) of the EFHLRTZilu options are passed to typeset;

whether we are OK with the implications of the foregoing when the -x
option is also present.