[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Possible bug in “kmous” in xterm-256color description
From: |
Mike O'Brien |
Subject: |
Re: Possible bug in “kmous” in xterm-256color description |
Date: |
Sun, 1 Aug 2021 15:53:03 -0700 |
I have now discovered how the “XM” entry in “xterm-256color” got deleted from
my copy of the terminfo database. It’s now been restored.
However, I now find that mouse position reporting is back to not working with
this entry. The “XM” entry apparently either isn’t sending the correct code to
turn on reporting, or there’s something borked in the entry. A modified
“xterm-256color” entry that I created, that reverts back to the “1002”
reporting method, however, does work, just FYI.
Thanks for your help!
Mike O'Brien
> On Aug 1, 2021, at 9:54 AM, Mike O'Brien <mikeobrien@spamcop.net> wrote:
>
> Well that explains it. The recent ncurses-6.2 distro I grabbed shows no “XM”
> entry for xterm-256color when I run this command.
>
>> On Aug 1, 2021, at 2:29 AM, Thomas Dickey <dickey@his.com> wrote:
>>
>> "1006"
>>
>> infocmp -1x xterm-256color |grep 1006
>>
>> XM=\E[?1006;1000%?%p1%{1}%=%th%el%;,
>>
>> ncurses sees the 1006 and turns on that mode.
>