Some extra information for this bug: If I specify the full path to the less binary, the problem goes away.
For example: $ less -S file Does not yield the same output as $ /usr/bin/less -S file This led me to believe there was another "less" someplace else on the system, however "which" verifies I am indeed running /usr/bin/less -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
