On Wed, Oct 16, 2024 at 09:54:32AM -0400, Greg Wooledge wrote: > On Wed, Oct 16, 2024 at 15:48:07 +0200, to...@tuxteam.de wrote: > > Exporting MORE set to some unknown option (I did MORE=-q) leads to > > more complaining and refusing service (so it seems to behave as if > > one passed that option directly in the command line). > > D'oh! > > What a disaster. OK, now I have a better understanding of why people > are complaining so vocally about this change.
:-) On a second reading I realize that my "more complaining" above can be read in two ways. Somehow... cute. > I still think that *conditionally* exporting MORE=-e (after performing > whatever version-number-checking backflips are needed) is going to be > a better solution than changing individual aliases one by one. Absolutely. Here's a rough sketch of what I'd go with: tomas@caliban:~$ more -e /dev/null > /dev/null 2>&1 && echo success => success tomas@caliban:~$ more -q /dev/null > /dev/null 2>&1 && echo success => So if more gets some funky option, it returns with a "bad" exit code. This might be a basis to set the MORE env var in some session-founding script. Besides, that dual (trial?) use of /dev/null is kinda... magic ;-) Cheers -- t
signature.asc
Description: PGP signature
