Skip to content

Fix scrolling over wrapped lines#109

Merged
hgwr merged 2 commits intomainfrom
codex/fix-cursor-jump-issue-on-line-wrap
Aug 9, 2025
Merged

Fix scrolling over wrapped lines#109
hgwr merged 2 commits intomainfrom
codex/fix-cursor-jump-issue-on-line-wrap

Conversation

@hgwr
Copy link
Owner

@hgwr hgwr commented Aug 9, 2025

Summary

  • keep window and cursor in sync when moving past long wrapped lines
  • add regression test for scrolling past top wrapped lines

Testing

  • cargo test --verbose
  • cargo build --verbose
  • pytest -n auto e2e --verbose

https://chatgpt.com/codex/tasks/task_e_6896df2888f8832fa1d7cc80714f82e5

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @hgwr, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

I've implemented a fix to improve the editor's scrolling behavior, specifically addressing issues where the cursor and window position would desynchronize when moving past long, wrapped lines. This change ensures that the editor maintains correct visual alignment and cursor placement, enhancing the overall navigation experience. Additionally, I've added a new end-to-end test to prevent similar issues from reappearing in the future.

Highlights

  • Cursor and Window Synchronization: I've addressed an issue where the editor's window and cursor could become out of sync when navigating past long lines that wrap, ensuring a smoother and more predictable user experience.
  • New Regression Test: I've introduced a new end-to-end regression test specifically designed to catch future regressions related to scrolling past wrapped lines, particularly when they appear at the top of the screen.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@hgwr hgwr merged commit e2b6924 into main Aug 9, 2025
1 check passed
@hgwr hgwr deleted the codex/fix-cursor-jump-issue-on-line-wrap branch August 9, 2025 05:52
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request fixes an issue with scrolling past wrapped lines by removing a call to move_end_of_line that had interfering side effects. A regression test is also added to cover this scenario. My review points out that while the scrolling is fixed, the underlying logic for cursor movement in NextLine is still not fully correct for wrapped lines and is inconsistent with PreviousLine. I've suggested a refactoring to address this for more robust behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant