bug#50116: Text on GNU grep webpage far too big

2021-08-19 Thread Antonio Diaz Diaz
Gavin Smith wrote: https://www.gnu.org/software/grep/manual/grep.html This documentation is not usable because the text is far too big. I assume it is being enlarged with a CSS file. Additionally, it inserts a pilcrow after each option, which may be confusing if one copies the text in an ema

bug#50116: Text on GNU grep webpage far too big

2021-08-19 Thread Steve Ward
On Thu, Aug 19, 2021 at 2:12 AM Gavin Smith wrote: > > https://www.gnu.org/software/grep/manual/grep.html > > This documentation is not usable because the text is far too big. I assume > it is being enlarged with a CSS file. > > > In the manual.css file [0], commenting out the font-size property

bug#50129: -f - option doesn't respond to single EOF from TTY.

2021-08-19 Thread Kaz Kylheku
This reproduces on grep 3.1 on Ubuntu. The command: grep -f - should accept a list of patterns from standard input, like this: $ grep -f - pat1 pat2 pat3 [Ctrl-D] Upon receiving the EOF indication (zero byte read), the program should immediately conclude that the list of pat

bug#50129: -f - option doesn't respond to single EOF from TTY.

2021-08-19 Thread Paul Jackson
My fading recollection from long, long ago is that this is a difficult to avoid artifact of using stdio. If no patterns are fed into grep, just a single EOF, then grep exits immediately. But some non-empty input (just a single "pat1" is sufficient) is fed to grep, then it takes two EOF's to get