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.

Sign up for GitHub

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

Jump to bottom

Blank window on neovim 0.92 #263

Closed
meluskyc opened this issue Sep 18, 2023 · 5 comments
Closed

Blank window on neovim 0.92 #263

meluskyc opened this issue Sep 18, 2023 · 5 comments

Comments

@meluskyc
Copy link
Contributor

neovim 0.92 had some changes that break the fvim UI.

grid_line now passes a wrap boolean. I'm guessing this is only useful for the TUI since I don't see neovide or other GUIs handling this yet. Unfortunately, this breaks pattern matching of the event. neovim/neovim@981acc2

grid_line can also send a cell with a repeat count of zero now. I don't think fvim does anything when cell.repeat is zero, so I'm not sure any changes are required for this.
meluskyc added a commit to meluskyc/fvim that referenced this issue Sep 18, 2023
@meluskyc
parse_grid_line: handle wrap yatli#263
2eea373 
neovim 0.92 added this to the event. This appears to be useful for the
TUI only, so for now let's just fix the pattern matching.
meluskyc added a commit to meluskyc/fvim that referenced this issue Sep 18, 2023
@meluskyc
parse_grid_line: handle wrap yatli#263
289b155 
neovim 0.92 added this to the event. This appears to be useful for the
TUI only, so for now let's just fix the pattern matching.
meluskyc added a commit to meluskyc/fvim that referenced this issue Sep 18, 2023
@meluskyc
parse_grid_line: handle wrap yatli#263
70c4c53 
neovim 0.92 added this to the event. This appears to be useful for the
TUI only, so for now let's just fix the pattern matching.
@meluskyc meluskyc mentioned this issue Sep 18, 2023
Merged
@jeremy-coleman
Copy link

blank screen for me too

@lost22git
Copy link

same problem

@kceiw
Copy link

kceiw commented Nov 10, 2023

Same problem here too.

@anosatsuk124
Copy link

anosatsuk124 commented Dec 2, 2023 •
edited
Loading

Same problem. And your @meluskyc fixes #264 works fine in my case. Thank you.

@yatli
Copy link
Owner

yatli commented Mar 23, 2024

Should be fixed with #264

@yatli yatli closed this as completed Mar 23, 2024
@yatli yatli mentioned this issue Mar 24, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@kceiw @meluskyc @yatli @jeremy-coleman @anosatsuk124 @lost22git