Python curses库调用getkey()后flash()仅生效一次的原因咨询

Great question—this is one of those tricky curses edge cases that ties into how the library interacts with terminal state and refresh mechanics. Let me break down what's happening:

What's causing the issue? #

The core problem comes from two key behaviors in curses:

1. How flash() works: curses.flash() sends a terminal control sequence directly (either a visual blink or an audible bell, depending on your terminal's support). It doesn't rely on curses' screen buffer, so it works fine when you're just looping and sleeping with no input calls.
2. What getkey() does under the hood: When you call stdscr.getkey(), curses automatically triggers a refresh() to sync the screen buffer with the terminal before waiting for input. This refresh resets the terminal's display state, clearing any pending visual effects like the flash. Worse, once the terminal enters input-wait mode (thanks to cbreak()), many terminal emulators prioritize input handling over visual feedback—so even after you press a key and the loop continues, the terminal might not respond to subsequent flash() sequences unless you explicitly nudge it.

How to fix it #

The simplest fix is to explicitly refresh the screen right after calling flash() to ensure the terminal processes the blink sequence before any input operations. Here's your modified code:

#! /usr/bin/env python3
import curses
def test(stdscr):
    import time
    curses.noecho()
    curses.cbreak()
    curses.curs_set(0)
    stdscr.keypad(True)
    while True:
        curses.flash()
        stdscr.refresh()  # Force terminal to process the flash sequence
        time.sleep(0.5)
        stdscr.getkey()
curses.wrapper(test)

Alternatively, you can use the window-specific stdscr.flash() instead of the global curses.flash()—sometimes window-level operations play nicer with curses' state management:

stdscr.flash()  # Replace curses.flash() with this

Why isn't this in the docs? #

Curses docs tend to focus on function basics rather than low-level terminal interactions. Since terminal emulators vary in how they handle control sequences and input states, these edge cases often aren't spelled out explicitly—you have to piece it together from how the library handles screen sync and terminal modes.

内容的提问来源于stack exchange，提问作者Denis