[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 145977] Konsole has a terminfo entry of its own;
From:       Alexander Toresson <alexander.toresson () gmail ! com>
Date:       2007-05-26 23:23:49
Message-ID: 20070526232349.10870.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=145977         




------- Additional Comments From alexander.toresson gmail com  2007-05-27 01:23 \
------- Hello Lars,

Thank you for an extremely informative and interesting explanation, I really \
appreciated it and learned a lot from it :)

So, the situation was a bit more complicated than I had thought.

Basically, the following is what terminfo would need to be able to describe:
* How to switch to the secondary screen
* How to switch back to the primary screen
* How to turn on mouse events (hmm, but getm might be enough already?)
* How to turn off mouse events

Another mouse capability I thought of that would enhance mouse support in terminals \
is support for motion events.

From http://www.linuxjournal.com/article/1136 :

"If you consider ever running your application under an xterm, you must be sure to \
not depend on a full event reporting. Specifically, you won't be informed of any \
motion or drag events, and button-release events won't specify which button of a set \
has been released. This means, in practice, that if you need precise reporting of a \
double-button press, your application will not work properly under xterm."

The first is what I suspected, that xterm doesn't support motion events. However, I \
don't understand the second problem. From what I've read, a 'release' is simply a \
'pressed' event sent once again to indicate that the button has been released.

Also, do you know what causes the window resize problem with TERM=konsole mc? I tried \
the same in vim, and it does seem to be able to handle it. I found out that there was \
terminfo capabilities named 'lines' and 'cols', but these don't seem to be it, as \
they're statically defined to certain numbers. I assume vim is always sending some \
xterm-specific CSI-code, while mc is only doing this if $TERM == 'xterm'?

Regards, Alexander Toresson


[prev in list] [next in list] [prev in thread] [next in thread]