Re: [PATCH 12/13] doc/bash.1: Fix *roff style nit.

2024-03-29 Thread Chet Ramey
On 3/28/24 5:12 PM, G. Branden Robinson wrote: While font mounting position 3 is usually assigned a bold typeface, it seems a bit fragile to not explicitly ask for bold. The concept of mounting positions is also not something man page authors typically need to think about. It's been like that

Re: > /dev/stderr 2>&-

2024-03-29 Thread Chet Ramey
On 3/29/24 9:32 AM, Greg Wooledge wrote: On Fri, Mar 29, 2024 at 09:02:12PM +1100, Reuben wrote: $ echo cat /dev/stderr > bug $ bash bug 2>&- cat /dev/stderr I don't understand what you were trying to do here. calling bash script 2>&- on linux seems to make /dev/stderr refer to script,

Re: install-headers stdckdint.h error

2024-03-29 Thread Grisha Levit
On Fri, Mar 29, 2024, 09:37 Chet Ramey wrote: > On 3/28/24 9:54 PM, Grisha Levit wrote: > > The addition of stdckdint.h to CREATED_HEADERS in Makefile.in leads to > > an error when installing loadable builtins on platforms that provide > > the header: > > Thanks for the report. What platform are

Re: install-headers stdckdint.h error

2024-03-29 Thread Chet Ramey
On 3/28/24 9:54 PM, Grisha Levit wrote: The addition of stdckdint.h to CREATED_HEADERS in Makefile.in leads to an error when installing loadable builtins on platforms that provide the header: Thanks for the report. What platform are you using that provides that header? -- ``The lyf so short,

Re: > /dev/stderr 2>&-

2024-03-29 Thread Greg Wooledge
On Fri, Mar 29, 2024 at 09:02:12PM +1100, Reuben wrote: > $ echo cat /dev/stderr > bug > $ bash bug 2>&- > cat /dev/stderr I don't understand what you were trying to do here. > calling bash script 2>&- on linux > seems to make /dev/stderr refer to script, > though &2 seems unaffected. > using

> /dev/stderr 2>&-

2024-03-29 Thread Reuben
$ echo cat /dev/stderr > bug $ bash bug 2>&- cat /dev/stderr calling bash script 2>&- on linux seems to make /dev/stderr refer to script, though &2 seems unaffected. using 2>&- inside script does not trigger this bug. i assume it is a bug and not 'historical compatibility'. the bug does not seem