[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: |
Tue, 19 Jan 2021 03:45:58 -0500 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
On Fri, Jan 15, 2021 at 11:22:33PM -0000, Grant Edwards wrote:
> I've recently been working with ncurses from Python, and would like to
...
> The basic 'problem' is that tputs and putp write to libc's FILE
> *stdout stream. Python's normal output mechanisms have their own
> buffering and write to file descriptor 1 instead of FILE
> *stdout. Therefore, "normal" Python output can't be mixed with putp()
> or tputs() calls without a fair amount of ugliness[1].
Actually, tputs doesn't necessarily write to stdout (the python
binding might need some work, but that's out of scope):
man tputs:
int tputs(const char *str, int affcnt, int (*putc)(int));
^^^^^^^^^^^^^^^^ (no stdout)
--
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net
ftp://ftp.invisible-island.net
signature.asc
Description: PGP signature
- Re: Using ncurses only for terminfo (no I/O), (continued)
- 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, 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 <=