fix: avoid crashing when nvim_win_set_option received invalid status line text #1190
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.
For some programming language there are some string formatting functions like
String.format("%d", a)
orprintf("%d", a")
. If lualine is combined withnvim_treesitter#statusline
like the following:It will sometimes crash when the code has
%
in it.For example,
the
%d
should be%%d
in status line text, but when the line gets too longnvim_treesitter#statusline
will try to trim the output text and replace with...
, and something the extra%
get trimmed off, which may look something like the followingand this would throw. (this trigger may differ for different screen widths)
one cheap solution is to wrap
vim.api.nvim_win_set_option
withpcall
. another solution would be to make surevim.api.nvim_win_set_option
is never called with a single%
.