View Single Post
Old 03-17-2024, 12:06 PM   #79
neil_swann80
0000000000101010
neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.
 
neil_swann80's Avatar
 
Posts: 5,895
Karma: 12981955
Join Date: Mar 2023
Location: An island off the coast of Ireland
Device: PB632 [HD3]
Quote:
Originally Posted by rkomar View Post
You can try closing descriptor '1' after the call to dup(), to see if that stops the pocketbook keyboard code from writing to standard output. You might also try adding "fflush(stdout);" to the beginning of the char_handler() function in case the keyboard code is writing to the stdout file stream. I'm not sure if either will work, but you might get lucky.
You legend!

Adding "fflush(stdout);" actually increased the amount of unneeded text, but closing descriptor '1' did it!

neil_swann80 is offline   Reply With Quote