We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
when I have rustyline configured the following way:
let config_builder = rustyline::config::Config::builder() .max_history_size(10000)? .history_ignore_dups( true)? .auto_add_history(true) .bell_style(rustyline::config::BellStyle::None) .completion_type(rustyline::config::CompletionType::List) .edit_mode( rustyline::EditMode::Vi); let config = config_builder.build();
(note that vi mode is active)
Later on I am in the commandline via:
rl.readline(">> ");
And I press 'ESC' (so I am in the command mode of the vi mode) and then I press '.' then it crashes.
>> thread 'main' panicked at 'internal error: entered unreachable code', .../.cargo/registry/src/github.com-1ecc6299db9ec823/rustyline-11.0.0/src/keymap.rs:205:18
'.' in the vi mode is the repetition of the latest command but in this situation there was no latest command yet.
Regards, Frank Schwidom
The text was updated successfully, but these errors were encountered:
Thanks for the detailed bug report.
Sorry, something went wrong.
Version 12.0.0 released
Successfully merging a pull request may close this issue.
Hi,
when I have rustyline configured the following way:
(note that vi mode is active)
Later on I am in the commandline via:
rl.readline(">> ");
And I press 'ESC' (so I am in the command mode of the vi mode)
and then I press '.' then it crashes.
>> thread 'main' panicked at 'internal error: entered unreachable code', .../.cargo/registry/src/github.com-1ecc6299db9ec823/rustyline-11.0.0/src/keymap.rs:205:18
'.' in the vi mode is the repetition of the latest command but in this situation there was no latest command yet.
Regards,
Frank Schwidom
The text was updated successfully, but these errors were encountered: