LSP Selection Changes After Selection #12170
Labels
C-bug
Category: This is a bug
Comments
|
Duplicate of #12119 |
|
Yep that version works. Thanks! I'd like to use the latest |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
With the new version of
rust-analyzer, I'm seeing an issue where selections will change right after selecting an option.To elaborate:
I'm typing
log_internal_and it comes up withlog_internal_server_error. I press to select the first option. The new text shows up. The new lsp suggestion for this location isassert_ne!. If I press Enter, Space, or any other key, the entirelog_internal_server_error(which I wanted) will be overwritten withassert_ne!which is completely different from what I was typing originally.I've upgraded from the rust-analyzer version that was out in May to
157c7d0114 2024-11-25both of which I compiled myself. I need this new version for Rust 1.82.This issue happens maybe 1/10 suggestions or less. I think it happens either because rust-analyzer is coming up with suggestions in places where it didn't used to, or the speed that it can come up with suggestions in some spots has greatly sped up.
If there was some delay for the user to deselect after choosing a suggestion, or if after selecting a suggestion it doesn't come up with a new selection, or if it deselects all text after choosing a suggestion, this issue would be fixed.
Reproduction Steps
I tried this:
I'm typing
log_internal_and it comes up withlog_internal_server_error. I press to select the first option. The new text shows up.I expected this to happen:
After pressing
log_internal_server_erroris completed and I can keep typing.Instead, this happened:
The new lsp suggestion for this location is
assert_ne!. If I press Enter, Space, or any other key, the entirelog_internal_server_error(which I wanted) will be overwritten withassert_ne!which is completely different from what I was typing originally.The only workaround I can find is to select an LSP option and hit enter extremely fast (before it can come up with a new suggestion). Sometimes I can't get the keystroke out fast enough and it happens again. It's very frustrating. You pretty much have to know the bug is coming and mentally prepare to hit enter super fast. If you overshoot, you'll just end up with a newline in your code... or you don't use lsp suggestions which sucks.
Helix log
~/.cache/helix/helix.log
I'm only posting logs from today. Also, I had to redact a lot.
Platform
Amazon Linux 2
Terminal Emulator
Alacritty
Installation Method
cargo
Helix Version
24.7 079f544
The text was updated successfully, but these errors were encountered: