editor: Accept next line prediction#44411
Merged
agu-z merged 12 commits intozed-industries:mainfrom Dec 15, 2025
Merged
Conversation
…oflexuous/zed into accept-next-line-prediction
…oflexuous/zed into accept-next-line-prediction
…oflexuous/zed into accept-next-line-prediction
…oflexuous/zed into accept-next-line-prediction
…oflexuous/zed into accept-next-line-prediction
…oflexuous/zed into accept-next-line-prediction
…oflexuous/zed into accept-next-line-prediction
|
We require contributors to sign our Contributor License Agreement, and we don't have @teleoflexuous on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'. |
Contributor
This comment was marked as resolved.
This comment was marked as resolved.
|
The cla-bot has been summoned, and re-checked this pull request! |
This comment was marked as outdated.
This comment was marked as outdated.
Contributor
|
@teleoflexuous Thank you for your contribution! This looks great 😄 |
CherryWorm
pushed a commit
to CherryWorm/zed
that referenced
this pull request
Dec 16, 2025
Closes [zed-industries#20574](zed-industries#20574) Release Notes: - Replaced editor action editor::AcceptPartialEditPrediction with editor::AcceptNextLineEditPrediction and editor::AcceptNextWordEditPrediction Tested manually on windows, attaching screen cap. https://github.com/user-attachments/assets/fea04499-fd16-4b7d-a6aa-3661bb85cf4f Updated existing test for accepting word prediction in copilot - it is already marked as flaky, not sure what to do about it and I'm not really confident creating new one without a working example. Added migration of keymaps and new defaults for windows, linux, macos in defaults and in cursor. This should alleviate [zed-industries#21645](zed-industries#21645) I used some work done in stale PR zed-industries#25274, hopefully this one makes it through! --------- Co-authored-by: Agus Zubiaga <agus@zed.dev>
SomeoneToIgnore
pushed a commit
that referenced
this pull request
Dec 16, 2025
…ion (#44971) ### Problem PR #44411 replaced the `editor::AcceptPartialEditPrediction` action with `editor::AcceptNextLineEditPrediction` and `editor::AcceptNextWordEditPrediction`. However, the Linux cursor keymap wasn't updated to reflect this change, causing a panic on startup for Linux users. ### Solution Updated the Linux keymap configuration to reference the new actions Release Notes: - N/A
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #20574
Release Notes:
Tested manually on windows, attaching screen cap. https://github.com/user-attachments/assets/fea04499-fd16-4b7d-a6aa-3661bb85cf4f
Updated existing test for accepting word prediction in copilot - it is already marked as flaky, not sure what to do about it and I'm not really confident creating new one without a working example.
Added migration of keymaps and new defaults for windows, linux, macos in defaults and in cursor.
This should alleviate #21645
I used some work done in stale PR #25274, hopefully this one makes it through!