search for: do_readln

...at I tried, the latter being a single executable that did the prompt and the timeout. (I can send code offline if anyone interested -- not fully protected against bad inputs, however.) Now I'm wondering where the code for readline is located in the R source. I've tracked as far as the 'do_readln' in names.c, but now want to find the actual code to see if I can patch it, though I am a real novice in C. Suggestions welcome. My application, FYI, is to have a script that will display something, and wait for a keypress (for readline it seems to need the Enter key) but timeout after a prese...

Neither do_menu nor do_readln (in src/main/scan.c) call the function InitConsoleGetchar. They need to do this to reset ConsolePrompt. If you use "scan" to read in data from the terminal, then ConsolePrompt is set to "n:" for some integer n and this prompt makes an unwelcome appearance when you use the &quot...

...()) may not be effective until a line is completed (i.e. ENTER is pressed). HOW UPDATING SOURCE CODE TO SUPPORT INTERRUPTS? I'm not sure where this "behavior" is originating from, and whether it is possible to obtain a cross-platform solution or not. I located the following native do_readln() function in src/main/scan.c that is called by readline(): SEXP attribute_hidden do_readln(SEXP call, SEXP op, SEXP args, SEXP rho) { ... while ((c = ConsoleGetchar())!= '\n' && c != R_EOF) { if (bufp >= &buffer[MAXELTSIZE - 2]) continue; *bufp++ = c; } ... }...

Dear R developers, I have found the following bug with readline() in R 0.63.3: if you execute the menu-function and then the readline() function, then readline() prompts "Selection:" > a <- readline() hello > a [1] "hallo" > a <- menu(c("a", "b"), title="bitte:") bitte: 1:a 2:b Selection: 2 > a <- readline() Selection: