| Main index | Section 3 | Options |
#include <curses.h>int get_wch(wint_t *wch); int wget_wch(WINDOW *win, wint_t *wch); int mvget_wch(int y, int x, wint_t *wch); int mvwget_wch(WINDOW *win, int y, int x, wint_t *wch);
int unget_wch(const wchar_t wc);
When input is pending, wget_wch stores an integer identifying the key stroke in wch; 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 subsections Keypad Mode and Predefined Key Codes in getch(3X).
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 wch to the window (at the cursor position) per the following rules.
| &#187; | If wch 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 wch to the window, as with wecho_wchar(3X). |
| &#187; | If the window has been moved or modified since the last call to wrefresh(3X), curses calls wrefresh. |
| &#187; | the WINDOW pointer is NULL, or |
| &#187; | its timeout expires without any data arriving, or |
| &#187; | execution was interrupted by a signal, in which case errno is set to EINTR. |
unget_wch returns OK on success and ERR if there is no more room in the input queue.
All of these functions except wget_wch and unget_wch may be implemented as macros.
Unlike wgetch(3X), wget_wch and its variants store the value of the input character in an additional wch parameter instead of the return value.
Unlike ungetch, unget_wch cannot distinguish function key codes wget_wch from conventional character codes. An application can overcome this limitation by pushing function key codes with ungetch and subsequently checking the return value of wget_wch for a match with KEY_CODE_YES.
X/Open Curses, Issue 4 describes these functions. It specifies no error conditions for them.
See the PORTABILITY section of wgetch(3X) regarding the interaction of wget_wch with signal handlers.
curses(3X), curs_add_wch(3X), curs_inopts(3X), curs_move(3X), curs_refresh(3X)
| 2024-04-20 | curs_get_wch (3X) | ncurses 6.5 |
| Main index | Section 3 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
| “ | Ken Thompson was once asked by a reporter what he would have changed about Unix if he had it all to do over again. His answer: “I would spell creat with an ‘e.'” | ” |