4 ms·
Only if your recent keystrokes have been getting echoed, and if you haven't done something that might disrupt echo. > Predictions are done in epochs: when the
by willglynn 10y ago
Only if your recent keystrokes have been getting echoed, and if you haven't done something that might disrupt echo.
> Predictions are done in epochs: when the user does something that might alter the echo behavior — like hit ESC or carriage return or an up- or down-arrow — Mosh goes back into making background predictions until a prediction from the new batch can be confirmed as correct.
- astazangasta 10y agoYeah, this offends me - I want my terminal to have simple, predictable behavior, not be trying to reason about what the shell process is up to. If it has some predictive model, I have to worry about my predictive model (expectation of what happens when I hit a key) being in conflict.
- fizzbatter 10y agoYou really don't have to worry about that, imo. The predictive feature doesn't overlap connectivity issues long enough for you to ever wonder "Am i connected or not"? Not to mention, it shows you in two ways that you have connectivity issues. 1. All echoing prints underlines, so you always know if it's predictive output or not. 2. Any prolonged connectivity issue displays a blue bar at the top of the session, showing how long you've been disconnected for. edit: And of course, you can simply turn off predictive echo if it's a feature you hate. but man oh man, is it something to love, imo.
- mikeash 10y agoAs opposed to having your non-predictive model be in conflict, because your connection decided to space out for a minute so you don't see any results from any of your typing?