Description of problem: Normal less functionality (cbreak mode to be precise) is broken by the LESSOPEN environment variable pointing to /usr/bin/lessopen.sh (okay, to a pipeline involving said script). Version-Release number of selected component (if applicable): less-378-7 How reproducible: 100% Steps to Reproduce: 1. Create or find a file containing more than one page of plain text. The output of 'lspci -v' may suffice. 2. Run less on that file, from a terminal window or equivalent. 3. After the first screenfull is visible, press the spacebar. Actual results: The space character is echoed, but the next screenful of text is not displayed. Expected results: The next screenful of text should be displayed. Additional info: Unsetting environment variable LESSOPEN appears to be a workaround.
I cannot reproduce this with LANG=de_DE.UTF-8 or LANG=en_US.UTF-8 and less-381. Which locale are you using and ?
I'm using LANG=en_US.UTF-8. What's really strange is I can't reproduce it now, either. I thought I had tested it on multiple terminals to make sure it wasn't just a hosed xterm (from somebody emailing characters above 0x7f) that was causing the symptom. You are welcome to mark this as "not a bug" and "customer was mistaken". Sorry for the false alarm.
closing. Please reopen when you find a way to reproduce this.
Okay, I found a way to reproduce it, when I do "less /etc/gconf/schemas/gnome-session.schemas" with the default LESSOPEN value, cbreak appears off, as in the spacebar is echoed, not acted on. This is with LANG set to en_US.UTF-8. Unsetting LESSOPEN makes less behave properly, as in the space bar works. I would guess it's tied to the non-ASCII, maybe multi-byte characters in the file, along with the LESSOPEN variable.