-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
CursorLineNr highlight disappears when moving up through folds #22232
Comments
Can't seem to reproduce for now, could you try to make a minimal reproducible example including |
I can reproduce a similar issue but it is present without
The cursor highlight is gone until the cursor is moved again(also when pressing the normal command keys instead). Can't reproduce a case where moving the cursor back and forth from the folded line keeps omitting the cursorline hightlight. |
This is labeled wrong because I didn't thoroughly investigate. That's my fault, I apologize. I can reproduce it consistently on HEAD with the below settings using
The real culprit in my setup are those mappings. Without them, the issue disappears. I'd like to relabel this issue, it is NOT the statuscolumn. |
Problem: The cursor line number was inaccurate when closing a fold and when moving to a closed fold with screenrow motions. Solution: Update cursor line number to the first line of the closed fold. Fix neovim#22232
Problem: The cursor line number was inaccurate when closing a fold and when moving to a closed fold with screenrow motions. Solution: Update cursor line number to the first line of the closed fold. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Problem: The cursorline highlight logic checks for `w_cursor.lnum` which may be different from the line number passed to `win_line()` even when the cursor is actually on that line. Solution: Update cursor line highlight logic to check for the line number of the start of a closed fold if necessary. Fix neovim#22232
Describe the bug
When using a the statuscolumn option and moving up the buffer line by line over folded text, the CursorLineNr highlight disappears. See the GIF below for an example.
Steps to reproduce
I can reproduce this with
o.statuscolumn = "%{v:relnum? v:relnum:v:lnum}"
.Expected behavior
The expected behavior is that the CursorLineNr highlight would not disappear when moving across folded text.
Neovim version (nvim -v)
NVIM v0.9.0-dev-934+g9668c166e,
Vim (not Nvim) behaves the same?
No, statuscolumn is not a vim feature
Operating system/version
Linux 6.1.9-arch1-2
Terminal name/version
xterm 378
$TERM environment variable
xterm-256color
Installation
build from repo
The text was updated successfully, but these errors were encountered: