Skip to content
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

String search jumps off-screen #6141

Closed
bcspragu opened this issue Feb 28, 2023 · 3 comments · Fixed by #6142
Closed

String search jumps off-screen #6141

bcspragu opened this issue Feb 28, 2023 · 3 comments · Fixed by #6142
Assignees
Labels
C-bug Category: This is a bug
Milestone

Comments

@bcspragu
Copy link
Contributor

Summary

I just built a new version of Helix at HEAD (8dab8a0) and the behavior of search (i.e. / then n) has broken such that the cursor and entry are always one-line off the bottom of the screen. I don't know what the previous behavior was (e.g. center of screen, bottom of screen), but it definitely wasn't this.

As a workaround I just type nzz to center the (otherwise not-visible) result.

Reproduction Steps

Should be readily reproducible, just search for a known string outside the current viewport.

Helix log

Not including this for now, can include if deemed helpful

Platform

Linux

Terminal Emulator

alacritty / tmux

Helix Version

helix 22.12 (8dab8a0)

@bcspragu bcspragu added the C-bug Category: This is a bug label Feb 28, 2023
@pascalkuthe
Copy link
Member

Do you have your scroff set to 0? I can reproduce the problem in that case but not otherwise. I think the refactor of the positioning code in #5420 simply as an off by 1 error here for the scroll-off at the bottom of the screen

@pascalkuthe pascalkuthe self-assigned this Feb 28, 2023
@pascalkuthe pascalkuthe added this to the next milestone Feb 28, 2023
@bcspragu
Copy link
Contributor Author

Do you have your scroff set to 0?

Yup, this was exactly the issue, not sure why I had that set in the first place, thanks!

@pascalkuthe
Copy link
Member

I would like to keep this open since it's still a regression that was unintentional. I will send a fix later

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants