reassign 178276 less
thanks
In recent versions of my gzip packaging, the zless script is just doing:
LESSOPEN="|gzip -cdfq -- %s"; export LESSOPEN
exec less "$@"
If I manually run that gzip command line against a gzip'ed zero-length file,
I get the expected null output. But zless behaves as the bug complans. So
I think what's happening is that less is trying to open the raw file as a
binary file if there's no output from the LESSOPEN command, or something like
that?
[EMAIL PROTECTED]:/tmp/foo$ touch emptyfile
[EMAIL PROTECTED]:/tmp/foo$ gzip emptyfile
[EMAIL PROTECTED]:/tmp/foo$ xxd emptyfile.gz
0000000: 1f8b 0808 dcae 7046 0003 656d 7074 7966 ......pF..emptyf
0000010: 696c 6500 0300 0000 0000 0000 0000 ile...........
[EMAIL PROTECTED]:/tmp/foo$ gzip -cdfq emptyfile.gz | xxd
[EMAIL PROTECTED]:/tmp/foo$ zless emptyfile.gz | xxd
"emptyfile.gz" may be a binary file. See it anyway? y
0000000: 1f8b 0808 dcae 7046 0003 656d 7074 7966 ......pF..emptyf
0000010: 696c 6500 0300 0000 0000 0000 0000 ile...........
[EMAIL PROTECTED]:/tmp/foo$
In any case, since the "problem" is because of something less is doing and
not something gzip is doing, I'm going to reassign this bug to less for
resolution.
Bdale
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
