[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Question about triggering KEY_MOUSE

From: Bryan Christ
Subject: Re: Question about triggering KEY_MOUSE
Date: Tue, 1 Jan 2019 22:33:36 -0600


I also see XM defined for VTE.  But that just raises yet another question for me as to how ncurses knows that something like xfce is really VTE even though TERM is set to xterm.

On Tue, Jan 1, 2019 at 6:29 PM Timothy Allen <address@hidden> wrote:
On Tue, 2019-01-01 at 17:20 -0600, Bryan Christ wrote:
Even with passing the -x param to infocmp, I still don't see XM defined for the four I queried:
xterm, konsole, xfce, rxvt

For reference, I'm using Debian Testing, with ncurses version 6.1+20181013-1.

I also don't see XM entries for xterm, konsole, xfce, rxvt, rxvt-unicode, or putty (or their 256 color variants, where available).

However, I do have XM entries for vte (the library GNOME Terminal is based on), nsterm (the terminal emulator that comes with macOS), iterm2 (a popular third-party terminal emulator for macOS), and terminology (the terminal emulator for the Enlightenment desktop environment). It's not present for screen itself (the terminal multiplexer), but it is present for a lot of the "sub entries" that represent the intersection of screen's capabilities with the outer terminal's. For example, PuTTY normally supports mode 1006, but Screen does not, so the screen.putty terminal definition has an XM string that says to use mode 1000.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]