No Cursor Jump on Commit Text Generation#32
Open
DamianB-BitFlipper wants to merge 1 commit intodouo:masterfrom
Open
No Cursor Jump on Commit Text Generation#32DamianB-BitFlipper wants to merge 1 commit intodouo:masterfrom
DamianB-BitFlipper wants to merge 1 commit intodouo:masterfrom
Conversation
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
1 participant
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.
Old Behavior
When I would stage files one by one in magit, the cursor would constantly jump to the GPT commit text line. That would then require me to navigate back up to the Staged menu entry. Repeat this and I am going down and up and down and up ...
New Behavior
Simply do not jump the cursor when GPT commit generation happens. This improves the usability immensely since I can stage files one after the other without the cursor position being affected.
Tested locally on my local installation.