-
Notifications
You must be signed in to change notification settings - Fork 32
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
Applying completion with placeholders causes cursor to jump to end of file #292
Comments
I realized that the jump is not always to the end of the file, but rather further down in the text viewer. Apparently the first occurrences were so far down in the source file, the cursor always just jumped to the end of the file. |
@Boereck Can you please try latest release of Corrosion and share some minimal steps to reproduce the issue? |
Hey @mickaelistria . I'll try later this evening. |
This is still happening to me, bot latest release and on master. In some cases it will not even accept place holder replacements on finish and remove characters after the placeholder . Super strange. |
Can you please provide some samples that allow to reproduce this issue + offsets of completion + expected vs actual result? |
When testing the Corrosion master with the LSP4E master, after applying a completion with placeholders (with or without variables like
$TM_SELECTED_TEXT
) and filling in all placeholders, the cursor position jumps to the end of the file. It does not matter if the completion comes from the RLS or the snippets defined by Corrosion. This may be an issue of LSP4E or an issue how Corrosion uses LSP4E (maybe the completions provide incomplete, or conflicting information).The text was updated successfully, but these errors were encountered: