GNU bug report logs - #62052
_N_GNU_nonoption_argv_flags_ is no longer supported

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 62052 in the body.
You can then email your comments to 62052 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Emanuele Torre <torreemanuele6 <at> gmail.com>
To: bug-grep <at> gnu.org
Subject: _N_GNU_nonoption_argv_flags_ is no longer supported
Date: Tue, 7 Mar 2023 17:40:59 +0100

Hello.

I have noticed the _N_GNU_nonoption_argv_flags_ (where N is the pid of
grep) environment variable mentioned in the documentation. I tried to
play with it, but it does not seem to work:

 bash-5.1$ (declare -x _"$BASHPID"_GNU_nonoption_argv_flags_=1111111
 > exec grep -e)
 grep: option requires an argument -- 'e'
 Usage: grep [OPTION]... PATTERNS [FILE]...
 Try 'grep --help' for more information.

I have checked gnulib's changelog and it looks like support for it has
been removed in 2017, and before that it has not been enabled by default
since 2001. (and, as far as I can tell, GNU grep never explicitly
enabled it.)

Furthermore, this environment variable used to be set this environment
variable automatically by bash up to version 2.0, but since version 2.01
(released in 1997) bash has stopped using it.

I think, at this point, it would be best to not mention that environment
variable in the documentation; it has not been used or even supported
for a long time so it is just confusing.

Bye. :)
 emanuele6

Message #10 received at 62052-done <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: Emanuele Torre <torreemanuele6 <at> gmail.com>
Cc: 62052-done <at> debbugs.gnu.org
Subject: Re: bug#62052: _N_GNU_nonoption_argv_flags_ is no longer supported
Date: Thu, 9 Mar 2023 06:39:47 -0800

[Message part 1 (text/plain, inline)]

On Wed, Mar 8, 2023 at 7:39 AM Emanuele Torre <torreemanuele6 <at> gmail.com> wrote:
> I have noticed the _N_GNU_nonoption_argv_flags_ (where N is the pid of
> grep) environment variable mentioned in the documentation. I tried to
> play with it, but it does not seem to work:
>
>  bash-5.1$ (declare -x _"$BASHPID"_GNU_nonoption_argv_flags_=1111111
>  > exec grep -e)
>  grep: option requires an argument -- 'e'
>  Usage: grep [OPTION]... PATTERNS [FILE]...
>  Try 'grep --help' for more information.
>
> I have checked gnulib's changelog and it looks like support for it has
> been removed in 2017, and before that it has not been enabled by default
> since 2001. (and, as far as I can tell, GNU grep never explicitly
> enabled it.)
>
> Furthermore, this environment variable used to be set this environment
> variable automatically by bash up to version 2.0, but since version 2.01
> (released in 1997) bash has stopped using it.
>
> I think, at this point, it would be best to not mention that environment
> variable in the documentation; it has not been used or even supported
> for a long time so it is just confusing.

Thank you for noticing and reporting that.
Done with the attached.

[grep-_N_GNU_nonoption_argv_flags_.patch (application/octet-stream, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.