In the simple setup you are likely using, getchar works with buffered input, so you have to press enter before getchar gets anything to read. Strings are not terminated by EOF; in fact, EOF is not really a character, but a magic value that indicates the end of the file. But EOF is not part … Read more
Your scanf only ate the number but not the trailing newline. Putting a newline or white space after the %d will then give you the opposite problem, reading too far. This is why people don’t like scanf. I would suggest reading an actual line (use fgets(3)) and then using sscanf() to scan the string.
#include <unistd.h> #include <termios.h> char getch(void) { char buf = 0; struct termios old = {0}; fflush(stdout); if(tcgetattr(0, &old) < 0) perror(“tcsetattr()”); old.c_lflag &= ~ICANON; old.c_lflag &= ~ECHO; old.c_cc[VMIN] = 1; old.c_cc[VTIME] = 0; if(tcsetattr(0, TCSANOW, &old) < 0) perror(“tcsetattr ICANON”); if(read(0, &buf, 1) < 0) perror(“read()”); old.c_lflag |= ICANON; old.c_lflag |= ECHO; if(tcsetattr(0, TCSADRAIN, … Read more
This depends on your OS, if you are in a UNIX like environment the ICANON flag is enabled by default, so input is buffered until the next ‘\n’ or EOF. By disabling the canonical mode you will get the characters immediately. This is also possible on other platforms, but there is no straight forward cross-platform … Read more