bug-ncurses
[Top][All Lists]
Advanced

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

Re: Using ncurses only for terminfo (no I/O)


From: Thomas Dickey
Subject: Re: Using ncurses only for terminfo (no I/O)
Date: Thu, 21 Jan 2021 15:01:54 -0500
User-agent: Mutt/1.10.1 (2018-07-13)

On Tue, Jan 19, 2021 at 03:10:51PM -0000, Grant Edwards wrote:
> On 2021-01-19, Thomas Dickey <dickey@his.com> wrote:
> > On Tue, Jan 19, 2021 at 06:35:11AM +0000, Nicholas Marriott wrote:
> >> On Mon, Jan 18, 2021 at 05:57:48PM -0000, Grant Edwards wrote:
> >>> On 2021-01-18, Nicholas Marriott <nicholas.marriott@gmail.com> wrote:
> >>> 
> >>>> tmux has been stripping padding from the result of tiget*() and writing
> >>>> it itself for 10 years now and I have had no problems reported
> >>>> whatsoever.
> >>> 
> >>> That's what my code currently does. One thing I'm wondering about is
> >>> what happens when a terminal control sequence contains a string like
> >>> $<5> that looks like a delay specification? Is that escaped somehow in
> >>> the database and then unescaped by putp() or tputs() when the padding
> >>> is added?
> >> 
> >> I don't know of any sequences which actually needs to output $<.
> 
> I don't either, but I couldn't see how that it was guaranteed not
> to. Were terminal manufacturers all aware of $<N> being reserved for
> terminfo strings and agreed not to use it?

probably not - some terminals encoded strings (DEC's did).

-- 
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net
ftp://ftp.invisible-island.net

Attachment: signature.asc
Description: PGP signature


reply via email to

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