Paolo, > Hello, would it be possible to have the echo char sent only after it > has been processed?
Currently a character is echo-ed when it got inserted into the input buffer. That involves the following steps 1.the usart module received it. An interrupt is triggered 2 the interrupt routine reads the character from the usart module and inserts it into the input buffer (a small ring buffer) 3 assuming we are in the command prompt: ACCEPT calls KEY and reads the character from the input buffer to the terminal input buffer (the 80+ input line). If the character is stored, it is echo-ed back to the usart (via EMIT). > In this case we could stop playing with timeout > tuning. When echo is received we could send another char or begin > transmit a new line (if last char was a newline), sure that the mcu > serial is idle and input will be correctly received. I think that an echo after a full line input is very unpleasant for interactive use. The timing optimizations are only necessary for dumb communications. The echo-flow control is proven to be very reliable and fast. > What do you think about? I think the current solution is better. Matthias ------------------------------------------------------------------------------ _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
