-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vi-style paren blinking causes unwanted "echo" in emacs #864
Comments
More specifically the erroneous output appears after calling I wonder if that line should be removed since Or if the condition |
@gnodet I would like to make a pull request to fix this, but would want some feedback on the approach before that. Would you have a moment to advice. |
With a dumb terminal, I'm even wondering if the read line loop which read bindings and evaluates widgets should be called at all. Given there's no line edition possible, I think the |
That's true. However, history should be stored because sbt provides even dump terminals ways to access the history. |
OTOH. Things such as history expansion would work equally on DUMP terminals (i.e. |
How about if we make a keymap for DUMP that only has a few things that will work in that environment? |
Yes, sounds a good idea. |
Actually we already have there the |
ping @gnodet. I would appreciate feedback on my fix (I have tested it on the repl and it works). Besides the |
This wasn't completed after all. The reason is that https://github.com/jline/jline3/blob/jline-parent-3.24.1/reader/src/main/java/org/jline/reader/impl/InputRC.java#L47 undoes what we implemented in LineReaderImpl. The line in |
@gnodet can you reopen the issue, it needs more fixing, see above comment |
When using
sbt
from emacs (throughsbt-mode
), the terminal is set not to echo. However, if the input line contains parenthesis, the line is partially repeated.Note on the last line the additional
"foo)
, which is not expected.The behavior is possibly caused by the vi-style paren blinking: https://github.com/jline/jline3/blob/master/reader/src/main/java/org/jline/reader/impl/LineReaderImpl.java#L2167
The question is, why is this functionality enabled for dumb terminals in sbt? Is there something wrong in how sbt uses jline3 or is it a bug in jline3 proper? I am available to help with a bug fix as soon as I understand which module to change.
The text was updated successfully, but these errors were encountered: