Hi, > Subject: Re: [PATCH v2] getopt.3: remove _<PID>_GNU_nonoption_argv_flags_ I've recently started specifying the full path of man-page files being modified. That makes it more consistent, and allows me to just use auto-completion for getting the file name. I haven't documented that yet, though. > Cc: Eugene Syromyatnikov <evgsyr@xxxxxxxxx> Please add those CCs to the commit trailer. Otherwise I have to paste them later. :) On Wed, Dec 18, 2024 at 03:35:28PM +0100, Ahelenia Ziemiańska wrote: > Per <https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=bf079e19f50d64aa5e05b5e17ec29afab9aabb20>: > * this was set by bash 2.0 (1996-12) > (implemented in glibc b07c5668f672125074dd5b0b658145e1544120be) > * it's no longer set by bash 2.01 (1997-06) because it was bad > * glibc disabled this with no way to enable it in 2001-08 > (518a0dd201c48a5c15d73c1919c304a9f8f5e3c1) > * glibc removed it in 2017 bf079e19f50d64aa5e05b5e17ec29afab9aabb20 For bullet lists (and any lists in general), I recommend using two spaces between the bullet and the text. See man-pages(7), and grep for /Lists$/. That helps differentiate between the bullet and the text more easily, especially in single-line entries. That was acked by Doug McIlroy when we talked about it. * *p is a pointee * *p is a pointee Makes sense? > > So this was experienced by people for 5 months at best, > and could remotely be experienced for 3 years > (if you somehow wanted this bad behaviour and added it into your shell), > over 20 years ago. No modern reader (or, frankly, non-modern reader) The right amount of inter-sentence space is two. I recently documented it here: <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTING.d/patches/description#n44> You'll find there a link to some interesting history about it: <https://web.archive.org/web/20171217060354/http://www.heracliteanriver.com/?p=324> > has ever used this, or could use it, really. > > Link to the removal note for completeness only. > > Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@xxxxxxxxxxxxxxxxxx> Thanks! I've applied the patch, plus minor tweaks for the issues above. <https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=fed899f4cd6149daa8c9a0f4c352728eadfd9d77> Have a lovely day! Alex > --- > man/man3/getopt.3 | 15 ++++++--------- > 1 file changed, 6 insertions(+), 9 deletions(-) > > diff --git a/man/man3/getopt.3 b/man/man3/getopt.3 > index 67c3ec9b3..9a84e2f44 100644 > --- a/man/man3/getopt.3 > +++ b/man/man3/getopt.3 > @@ -318,15 +318,6 @@ .SH ENVIRONMENT > .B POSIXLY_CORRECT > If this is set, then option processing stops as soon as a nonoption > argument is encountered. > -.TP > -.B _<PID>_GNU_nonoption_argv_flags_ > -This variable was used by > -.BR bash (1) > -2.0 to communicate to glibc which arguments are the results of > -wildcard expansion and so should not be considered as options. > -This behavior was removed in > -.BR bash (1) > -2.01, but the support remains in glibc. > .SH ATTRIBUTES > For an explanation of the terms used in this section, see > .BR attributes (7). > @@ -391,6 +382,12 @@ .SH HISTORY > for this purpose as LEGACY. > POSIX.1-2001 does not require the declaration to appear in > .IR <stdio.h> . > +.P > +Very old versions of glibc were affected by a > +.UR https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=bf079e19f50d64aa5e05b5e17ec29afab9aabb20 > +.BI _ PID _GNU_nonoption_argv_flags_ > +environment variable > +.UE . > .SH NOTES > A program that scans multiple argument vectors, > or rescans the same vector more than once, > -- > 2.39.5 -- <https://www.alejandro-colomar.es/>
Attachment:
signature.asc
Description: PGP signature
