Re: stty default output/-a _POSIX_VDISABLE character "undef", contrasts with "" on all known implementations? Formatting loss->overinterpretation since Issue 6.

Hi наб, Thank you for your work on this issue. It has been filed as Austin Group Defect Tracker issue #1604. See https://austingroupbugs.net/view.php?id=1604 Cheers, Don > On Sep 10, 2022, at 5:09 AM, наб via austin-group-l at The Open Group > wrote: > > Hi! > > Issue 7 and Issue 8 Draft

Re: stty default output/-a _POSIX_VDISABLE character "undef", contrasts with "" on all known implementations? Formatting loss->overinterpretation since Issue 6.

наб wrote in <20220910120939.iujppzbqbw4al...@tarta.nabijaczleweli.xyz>: ... |This is very curious! /I/ was very curious, at least. ... |My naive interpretation of this is that, after loss of monospacing from |POSIX.2 to SUSv1, at some point in Issue 6's creation, "" was |taken to mean

stty default output/-a _POSIX_VDISABLE character "undef", contrasts with "" on all known implementations? Formatting loss->overinterpretation since Issue 6.

Hi! Issue 7 and Issue 8 Draft 2.1 say this (XCU, stty, STDOUT, last para.): If control characters are written as part of the default output, or if the −a option is specified, control characters shall be written as: "%s = %s;", , where is either the character, or some visual