| Main index | Section 3 | Options |
#include <curses.h>int getch(void); int wgetch(WINDOW *win); int mvgetch(int y, int x); int mvwgetch(WINDOW *win, int y, int x);
int ungetch(int c);
/* extension */ int has_key(int c);
When input is pending, wgetch returns an integer identifying the key stroke; for alphanumeric and punctuation keys, this value corresponds to the character encoding used by the terminal. Use of the control key as a modifier often results in a distinct code. The behavior of other keys depends on whether win is in keypad mode; see subsection Keypad Mode below.
If no input is pending, then if the no-delay flag is set in the window (see nodelay(3X)), the function returns ERR; otherwise, curses waits until the terminal has input. If cbreak(3X) has been called, this happens after one character is read. If nocbreak(3X) has been called, it occurs when the next newline is read. If halfdelay(3X) has been called, curses waits until a character is typed or the specified delay elapses.
If echo(3X) has been called, and the window is not a pad, curses writes the returned character c to the window (at the cursor position) per the following rules.
| &#187; | If c matches the terminal's erase character, the cursor moves leftward one position and the new position is erased as if wmove(3X) and then wdelch(3X) were called. When the window's keypad mode is enabled (see below), KEY_LEFT and KEY_BACKSPACE are handled the same way. |
| &#187; | curses writes any other c to the window, as with wechochar(3X). |
| &#187; | If the window has been moved or modified since the last call to wrefresh(3X), curses calls wrefresh. |
| &#187; | The curses.h header file declares many predefined function keys whose names begin with KEY_; these object-like macros have values outside the range of eight-bit character codes. |
| &#187; | In ncurses, user-defined function keys are configured with define_key(3X); they have no names, but are also expected to have values outside the range of eight-bit codes. |
Most terminals one encounters follow the ECMA-48 standard insofar as their function keys produce character sequences prefixed with the escape character ESC. This fact implies that curses cannot know whether the terminal has sent an ESC key stroke or the beginning of a function key's character sequence without waiting to see if, and how soon, further input arrives. When curses reads such an ambiguous character, it sets a timer. If the remainder of the sequence does not arrive within the designated time, wgetch returns the prefix character; otherwise, it returns the function key code corresponding to the unique sequence defined by the terminal. Consequently, a user of a curses application may experience a delay after pressing ESC while curses disambiguates the input; see section EXTENSIONS below. If the window is in no time-out mode, the timer does not expire; it is an infinite (or very large) value. See notimeout(3X). Because function key sequences usually begin with an escape character, the terminal may appear to hang in no time-out mode after the user has pressed ESC. Generally, further typing awakens curses.
| &#187; | Except for the special case of KEY_RESIZE, a window's keypad mode must be enabled for wgetch to read these codes from it. | ||
| &#187; | Not all of these are necessarily supported on any particular terminal. | ||
| &#187; |
The naming convention may seem obscure,
with some apparent misspellings
(such as RSUME for resume);
the names correspond to the
term info capability names for the keys,
and were standardized before the IBM PC/AT keyboard layout achieved a
dominant position in industry.
| ||
Two of the symbols in the list above do not correspond to a physical key.
| &#187; | wgetch returns KEY_RESIZE, even if the window's keypad mode is disabled, when ncurses handles a SIGWINCH signal; see initscr(3X) and resizeterm(3X). |
| &#187; | wgetch returns KEY_MOUSE to indicate that a mouse event is pending collection; see curs_mouse(3X). Receipt of this code requires a window's keypad mode to be enabled, because to interpret mouse input (as with with xterm(1)'s mouse prototocol), ncurses must read an escape sequence, as with a function key. |
Functions taking a WINDOW pointer argument fail if the pointer is NULL.
Functions prefixed with mv first perform cursor movement and fail if the position (y, x) is outside the window boundaries.
wgetch also fails if
| &#187; | its timeout expires without any data arriving, or |
| &#187; | execution was interrupted by a signal, in which case errno is set to EINTR. |
has_key returns TRUE or FALSE.
Some key strokes are indistinguishable from control characters; for example, KEY_ENTER may be the same as ^M, and KEY_BACKSPACE may be the same as ^H or ^?. Consult the terminal's term info entry to determine whether this is the case; see infocmp(1). Some curses implementations, including ncurses, honor the term info key definitions; others treat such control characters specially.
curses distinguishes the Enter keys in the alphabetic and numeric keypad sections of a keyboard because (most) terminals do. KEY_ENTER refers to the key on the numeric keypad and, like other function keys, and is reliably recognized only if the window's keypad mode is enabled.
| &#187; | The term info key_enter (kent) capability describes the character (sequence) sent by the Enter key of a terminal's numeric (or similar) keypad. |
| &#187; | Enter or send is X/Open Curses's description of this key. |
| &#187; | It usually produces a control code for carriage return (^M) or line feed (^J). |
| &#187; | Depending on the terminal mode (raw, cbreak, or cooked), and whether nl(3X) or nonl(3X) has been called, wgetch may return either a carriage return or line feed upon an Enter or Return key stroke. |
Historically, the list of key code macros above was influenced by the function-key-rich keyboard of the AT&T 7300 (also known variously as the 3B1, Safari 4, and UNIX PC), a 1985 machine. Today's computer keyboards are based that of the IBM PC/AT and tend to have fewer. A curses application can expect such a keyboard to transmit key codes KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_HOME, KEY_END, KEY_PPAGE (Page Up), KEY_NPAGE (Page Down), KEY_IC (Insert), KEY_DC (Delete), and KEY_F(n) for 1 ≤ n ≤ 12.
getch, mvgetch, and mvwgetch may be implemented as macros.
has_key was designed for ncurses(3X), and is not found in SVr4 curses, 4.4BSD curses, or any other previous curses implementation.
X/Open Curses, Issue 4 describes getch, wgetch, mvgetch, mvwgetch, and ungetch. It specifies no error conditions for them.
wgetch reads only single-byte characters.
The echo behavior of these functions on input of KEY_ or backspace characters was not specified in the SVr4 documentation. This description is adapted from X/Open Curses.
The behavior of wgetch in the presence of signal handlers is unspecified in the SVr4 documentation and X/Open Curses. In historical curses implementations, it varied depending on whether the operating system's dispatch of a signal to a handler interrupting a read(2) call in progress, and also (in some implementations) whether an input timeout or non-blocking mode has been set. Programmers concerned about portability should be prepared for either of two cases: (a) signal receipt does not interrupt wgetch; or (b) signal receipt interrupts wgetch and causes it to return ERR with errno set to EINTR.
KEY_MOUSE is mentioned in X/Open Curses, along with a few related term info capabilities, but no higher-level functions use the feature. The implementation in ncurses is an extension.
KEY_RESIZE and has_key are extensions first implemented for ncurses. By 2022, PDCurses and NetBSD curses had added them along with KEY_MOUSE.
curses(3X), curs_addch(3X), curs_inopts(3X), curs_mouse(3X), curs_move(3X), curs_outopts(3X), curs_refresh(3X), curs_variables(3X), resizeterm(3X), ascii(7)
ECMA-6 7-bit coded Character Set <https://ecma-international.org/ publications-and-standards/standards/ecma-6/>
ECMA-48 Control Functions for Coded Character Sets <https://ecma-international.org/ publications-and-standards/standards/ecma-48/>
| 2024-04-20 | curs_getch (3X) | ncurses 6.5 |
| Main index | Section 3 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
| “ | Hang in there, people suffering from natural disasters and deadly diseases - we're putting ribbons on our cars as fast as we can | ” |
| — Artur Bagyants | ||