Re: [1003.1(2016/18)/Issue7+TC2 0001384]: Subshell of an interactive shell is effectively non-interactive

On 11/01/2021 16:45, Austin Group Bug Tracker via austin-group-l at The Open Group wrote: shall be set to the default action.If the shell is interactive, the subshell shall behave as a non-interactive shell in all respects except:The expansion of the special parameter '-' and the output of set

[1003.1(2016/18)/Issue7+TC2 0001385]: unlink() text needs updating to account for mmap()

The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=1385 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001384]: Subshell of an interactive shell is effectively non-interactive

The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=1384 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001384]: Subshell of an interactive shell is effectively non-interactive

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1384 == Reported By:geoffclare Assigned To:

Re: Bug 1393 ("command" declaration utility) possible solution

Martijn Dekker wrote, on 09 Jan 2021: > > Op 23-09-20 om 15:11 schreef Geoff Clare via austin-group-l at The Open > Group: > > > > In order to make "command export ..." and "command readonly ..." > > work the same, all that's necessary is for those shells to treat > > command as a separate token