[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:35:11 +0000 |
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.
- Using ncurses only for terminfo (no I/O), Grant Edwards, 2021/01/15
- Re: Using ncurses only for terminfo (no I/O), Thomas Dickey, 2021/01/15
- Re: Using ncurses only for terminfo (no I/O), Timothy Allen, 2021/01/15
- Re: Using ncurses only for terminfo (no I/O), Nicholas Marriott, 2021/01/18
- Re: Using ncurses only for terminfo (no I/O), Grant Edwards, 2021/01/18
- Re: Using ncurses only for terminfo (no I/O), Thomas Dickey, 2021/01/18
- Re: Using ncurses only for terminfo (no I/O),
Nicholas Marriott <=
- Re: Using ncurses only for terminfo (no I/O), Nicholas Marriott, 2021/01/19
- Re: Using ncurses only for terminfo (no I/O), Thomas Dickey, 2021/01/19
- Re: Using ncurses only for terminfo (no I/O), Grant Edwards, 2021/01/19
- Re: Using ncurses only for terminfo (no I/O), Thomas Dickey, 2021/01/21
Re: Using ncurses only for terminfo (no I/O), Thomas Dickey, 2021/01/19