Hi Adeodato, Sorry it's taken so long for me to get back to this. I think the behavior of less-393 is actually more correct than less-382. The man page says that -r displays raw control characters, while -R only outputs ANSI "color" escape sequences in raw form. Your file contains escape sequences other than color sequences, to draw the lines that make up the tree. So the fact that -R worked in less-382 is arguably a bug. The documentation guarantees only that color escapes will work with -R. So I think the bottom line is that less-393 is working according to the documentation. Let me know if you disagree.
--Mark On 11/6/2005 1:26 PM, Adeodato Simó wrote: > * Mark Nudelman [Sun, 06 Nov 2005 13:12:10 -0800]: > > >>Hi Adeodato, > > > Hi! > > >>Thank you for your bug report. I have a few questions about this problem. > > > Uhm, first of all, while trying to answer your questions below, I just > found out that using -r instead of -R fixes my problem. I don't know > the relevance of this, though. > > >>1. Do you experience this problem with the latest version (less-393)? > > > Yes. > > >>2. How do you have your locale environment variables set (LANG, LC_TYPE, >>LC_ALL, LESSCHARSET, LESSCHARDEF)? > > > LANG=es_ES.UTF-8 > LC_NUMERIC=C > LC_TIME=C > LC_COLLATE=C > LC_MESSAGES=C > > LC_ALL, LESSCHARSET, and LESSCHARSET: unset > > >>3. Are you using the -r or -R flags (either explicitly, or in your LESS >>environment variable, or in your lesskey file)? Did you use them when >>you used version 382? > > > Yes, -R (LESS="-c -g -i -M -R -S"). But as said above, using -r makes > 393 work ok, while 382 works fine with-R. > > >>4. Can you put the raw output of the tree program in a file, like this: >> tree -CAN > tree.out >>Then verify that >> less tree.out >>exhibits the problem. If that works, please send me the tree.out file. > > > It exhibits the problem. File attached. > > >>Thanks, > > > Cheers, > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
