Bug#885710: marked as done (RFS: libt3key/0.2.7-1 ITP #885595)
Your message dated Tue, 2 Jan 2018 04:10:50 +0100
with message-id <email@example.com>
and subject line Re: Bug#885710: RFS: libt3key/0.2.7-1 ITP #885595
has caused the Debian Bug report #885710,
regarding RFS: libt3key/0.2.7-1 ITP #885595
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact firstname.lastname@example.org
Debian Bug Tracking System
Contact email@example.com with problems
--- Begin Message ---
- To: firstname.lastname@example.org
- Subject: RFS: libt3key/0.2.7-1 ITP #885595
- From: Gertjan Halkes <email@example.com>
- Date: Fri, 29 Dec 2017 13:30:46 +0100
- Message-id: <firstname.lastname@example.org>
I am looking for a sponsor for my package "libt3key". This is one of
the dependencies of the Tilde text editor (#692512).
* Package name : libt3key
Version : 0.2.7-1
Upstream Author : Gertjan Halkes
* URL : https://os.ghalkes.nl/t3/libt3key.html
* License : GPL
Section : libs
It builds those binary packages:
libt3key-bin - Utilities for working with libt3key terminal
libt3key-dev - Development files for libt3key
libt3key1 - Terminal key sequence database library
To access further information about this package, please visit the
Alternatively, one can download the package with dget using this
Thanks in advance,
--- End Message ---
--- Begin Message ---
- To: Gertjan Halkes <email@example.com>, firstname.lastname@example.org
- Subject: Re: Bug#885710: RFS: libt3key/0.2.7-1 ITP #885595
- From: Adam Borowski <email@example.com>
- Date: Tue, 2 Jan 2018 04:10:50 +0100
- Message-id: <firstname.lastname@example.org>
- In-reply-to: <email@example.com>
- References: <firstname.lastname@example.org>
On Fri, Dec 29, 2017 at 01:30:46PM +0100, Gertjan Halkes wrote:
> I am looking for a sponsor for my package "libt3key". This is one of
> the dependencies of the Tilde text editor (#692512).
> * Package name : libt3key
> Version : 0.2.7-1
> libt3key-bin - Utilities for working with libt3key terminal
> libt3key-dev - Development files for libt3key
> libt3key1 - Terminal key sequence database library
Uploaded, in NEW.
I wanted to write a library doing this very thing, for about two decades,
yet somehow never had the tuits to do so. Instead, I wrote ad-hoc hacks
every time I needed this, ranging from okayish:
to utter crock:
I agree with you that curses is poo -- and it always was. I migrated off
it as sshing between IRIX, Linux and Solaris boxes meant that you lost not
only colors but even spaces (resultingintextlookinglikethis). Even modern
versions, despite efforts of a competent maintainer, are doomed to lose for
* sticking to an ancient API that's centered around pre-vt100 terminals
* using termcap/terminfo
The last part needs stressing: both stopped being maintained by mid-1980s.
Did you perhaps hear of a new-fangled kernel/OS named "Linux", that was
quite a rage in the '90s, and perhaps might see some use to this day? It
turns out guys at Sun/Oracle did not, and even most recent versions of
Solaris still don't understand TERM=linux (vt might not see as much use
today, but some of us still care about it).
Thus, thank you a lot for writing this!
However, the documentation is not only inadequate, but pretty much not
For example, the only major text is for definition format, and even that is
lacking. Like, what's "kx"? All I see is that it's something that's off on
TERM=linux and TERM=rxvt, a bit of poking around shows it's related to
keypad application mode, which makes it being off on linux and rxvt a bit
odd as these two terminals do it most sanely ("\e=" without a need to mess
with modes, some return values differing from vt100 and friends, etc). I
did not source-dive here on a purpose -- a typical user would turn away in
disgust if no documentation is provided.
The API seems to be not documented at all, other than some unclear comments
in .h files.
The other issue is that, in my opinion, you rely on the TERM variable way
too much. Its value tends to be useless (pretty much anything says it's
"xterm" -- for some horrors, you can look especially at terminals popular in
Windows lands), or outright missing/wrong (lxc-attach, serial consoles).
>From my experience, the only semi-reliable way to detect between major
terminal types is to print "\e[>c" and listen for response. (And while
we're here, http://angband.pl/software/tty/sizetty.c for when TIOCGWINSZ
. git shortlog v4.14 --author='Adam Borowski' shows my score as
18-out-of-27 kernel commits being to vt.c
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets. Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.
--- End Message ---