[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using ncurses only for terminfo (no I/O)
From: |
Timothy Allen |
Subject: |
Re: Using ncurses only for terminfo (no I/O) |
Date: |
Sat, 16 Jan 2021 12:59:02 +1100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 |
On 16/1/21 10:22, Grant Edwards wrote:
bold = curses.tigetstr('bold').decode('ascii')
Not strictly relevant to your tputs/tparm conundrum, just a
suggestion. You can avoid all that messing with decode('ascii') if
you write to the inner byte I/O handle instead of the Unicode I/O
wrapper:
write = sys.stdout.buffer.write
Tim.
- 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 <=
- 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, 2021/01/19
- 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