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: Nicholas Marriott
Subject: Re: Using ncurses only for terminfo (no I/O)
Date: Tue, 19 Jan 2021 06:37:36 +0000

Well that may not work if actually using tputs, I don't actually know
what would work, Thomas might be able to tell you. Although this has
never come up so I doubt there are any entries where it is necessary, at
least not in common use.


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 $<. Padding
> is stripped before expansion by tparm so I expect the $ could be
> replaced by %'$' or some other sequence.



reply via email to

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