[1003.1(2016/18)/Issue7+TC2 0001555]: -a/allexport spec should cover ${var=value} and ${var:=value}

The following issue has been UPDATED. == https://austingroupbugs.net/view.php?id=1555 == Reported By:McDutchie Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001555]: -a/allexport spec should cover ${var=value} and ${var:=value}

The following issue NEEDS AN INTERPRETATION. == https://austingroupbugs.net/view.php?id=1555 == Reported By:McDutchie Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001555]: -a/allexport spec should cover ${var=value} and ${var:=value}

The following issue has been set as RELATED TO issue 0001009. == https://austingroupbugs.net/view.php?id=1555 == Reported By:McDutchie

[Issue 8 drafts 0001556]: clarify meaning of \n used in a bracket expression in a sed context address or s-command

The following issue has been set as RELATED TO issue 0001550. == https://austingroupbugs.net/view.php?id=1556 == Reported By:calestyo

[Issue 8 drafts 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

The following issue has been set as RELATED TO issue 0001556. == https://austingroupbugs.net/view.php?id=1550 == Reported By:calestyo

[1003.1(2016/18)/Issue7+TC2 0001546]: BREs: reserve \? \+ and \|

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

[1003.1(2013)/Issue7+TC1 0001009]: "remain in affect after" and "during the execution" are problematic when built-in/function modifies the variable

The following issue has been set as RELATED TO issue 0001555. == https://austingroupbugs.net/view.php?id=1009 == Reported By:rhansen