Re: Bug#363250: general: Custom PAGER gives error on sid, but works on sarge
Henning Makholm <email@example.com> writes:
> Policy does not really specify how to handle $PAGER and its friends,
> but I have always assumed that it was OK for a package to do things
> like (error checking omitted for clarity):
> In that case, PAGER has to be set to just the name of a program, with
> no parameters or metacharacters embedded.
I don't think this agrees very well with historical practice though --
I've had PAGER set to something like "less -s" for _decades_, and never
had any problems, on more unix variants than I care to think about...
If a program doesn't allow this, I think it's buggy.
If debian specifies PAGER more exactly, the specification should _at
least_ allow for space-separated options and require PATH searching.
Do not taunt Happy Fun Ball.