© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
[TL;DR: Bash developer Chet Ramey claimed in 2015 that this is a documentation bug. Then, in 2016, a documentation patch has been proposed to (and possibly accepted by?) Debian.]
On 16 Sep 2016, Chet Ramey released version 4.4 of bash. This inspired me to check and see if this long standing issue has been fixed. Here is what I learned.
Debian bug # 343673 from 2005.
https:/
Debian bug # 516152 from 2009.
https:/
GNU Savannah bug #107950 from 2012.
https:/
In 2015, Chet Ramey commented on the above Savannah bug report:
"Debian made that documentation error. If you compile with -DSYS_BASHRC, it's always executed, as is ~/.bashrc (or the file specified with --rcfile)"
In other words, Ramey claims this is a documentation bug. I do not know if -DSYS_BASHRC has only the one above effect, or if it also has other effects as well.
In 2016, Tom Levy posted the following comment on Debian bug #516152 (see above link).
"Convincing Chet that the behaviour in Debian's documentation is preferable
to the current behaviour seems hard considering his 3-year response time. I propose changing the documentation."
Levy also included a patch to Debian's bash man page. The patch is here:
https:/
I am not an expert on the Debian development process, so I am unable to determine if the patch has been accepted by Debian.
The patch does not appear to have been applied to the following file, but this might not be the correct place to look for the patch. (Again, I am not a Debian expert.)
http://