bug#47243: pr lacks -p

Pádraig Brady writes: > On 30/07/2025 18:31, Paul Eggert wrote: >> On 2025-07-30 04:18, Pádraig Brady wrote: >>> I'd have a slight preference for _not_ gating the isatty(STDOUT) check >>> on $POSIXLY_CORRECT. >>> We generally only use $POSIXLY_CORRECT to gate incompatible behavior. >> Sure, but d

bug#79130: Change/feature requests chcon/chgrp/chmod/chown/touch

On 30/07/2025 09:05, Martin D Kealey wrote: I would like the 'chown -h' and 'chcon -h' to work the same way as 'touch -h': as well as not following symlinks for targets, they should also not follow a symlink given as --reference=. For consistency it probably makes sense for `chmod -h` to also n

bug#47243: pr lacks -p

Paul Eggert writes: > On 2025-07-29 21:51, Collin Funk wrote: > >> + /* Just exit if the user presses Ctrl-D. */ >> + if (bytes_read == 0) >> +return; > > This needs reworking now that 'pause_maybe' is a separate function, as > the code no longer exits, it just keep

bug#79130: Change/feature requests chcon/chgrp/chmod/chown/touch

On 2025-07-30 01:05, Martin D Kealey wrote: I would like the 'chown -h' and 'chcon -h' to work the same way as 'touch -h': as well as not following symlinks for targets, they should also not follow a symlink given as --reference=. Makes sense to me. Let's see what others think. If the patch is

bug#47243: pr lacks -p

On 2025-07-29 21:51, Collin Funk wrote: + /* Just exit if the user presses Ctrl-D. */ + if (bytes_read == 0) +return; This needs reworking now that 'pause_maybe' is a separate function, as the code no longer exits, it just keeps going. One other thought. It ma

bug#47243: pr lacks -p

On 2025-07-30 11:29, Pádraig Brady wrote: On 30/07/2025 18:31, Paul Eggert wrote: On 2025-07-30 04:18, Pádraig Brady wrote: I'd have a slight preference for _not_ gating the isatty(STDOUT) check on $POSIXLY_CORRECT. We generally only use $POSIXLY_CORRECT to gate incompatible behavior. Sure, b

bug#47243: pr lacks -p

On 30/07/2025 18:31, Paul Eggert wrote: On 2025-07-30 04:18, Pádraig Brady wrote: I'd have a slight preference for _not_ gating the isatty(STDOUT) check on $POSIXLY_CORRECT. We generally only use $POSIXLY_CORRECT to gate incompatible behavior. Sure, but don't the GNU coding standards disagree

bug#47243: pr lacks -p

On 2025-07-30 04:18, Pádraig Brady wrote: I'd have a slight preference for _not_ gating the isatty(STDOUT) check on $POSIXLY_CORRECT. We generally only use $POSIXLY_CORRECT to gate incompatible behavior. Sure, but don't the GNU coding standards disagree with POSIX here? If we follow the GNU c

bug#79130: Change/feature requests chcon/chgrp/chmod/chown/touch

I searched the archives and it appears there was a related discussion in bug#61720 , but that focused on aligning the documentation with the behaviour rather than the other way around. I've been using touch+chown+chmod+chcon with the --reference

bug#47243: pr lacks -p

On 30/07/2025 05:51, Collin Funk wrote: Paul Eggert writes: +After printing each page, print an alert (bell) to standard error and +wait for a newline to be read from @file{/dev/tty} before printing the +next page. This sentence should start "Before" not "After", with the rest of the sentenc