-
Notifications
You must be signed in to change notification settings - Fork 476
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
Bug: Not enough room #872
Comments
Thanks for making a proper issue. It's an upstream bug. You can follow neovim/neovim#19464 |
tapayne88
added a commit
to tapayne88/dotfiles
that referenced
this issue
Dec 31, 2022
Stumbled upon this issue. My workaround: {
"filename",
path = 1,
fmt = function(filename)
-- Small attempt to workaround https://github.com/nvim-lualine/lualine.nvim/issues/872
if #filename > 80 then
filename = vim.fs.basename(filename)
end
if #filename > 80 then
return string.sub(filename, #filename - 80, #filename)
end
return filename
end,
}, If someone has the same issue while waiting for the upstream to be fixed. |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Self Checks
How to reproduce the problem
Place a cursor on a block which the matching closing or opening is out of the viewport (ex:
{
and the matching}
is out of the viewport) and press%
Expected behaviour
No error shown and I can navigate to the matching block.
Actual behaviour
This error is shown:
Minimal config to reproduce the issue
minimal.lua:
The text was updated successfully, but these errors were encountered: