You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
With narrow fonts (e.g. Iosevka), devicons are located too close to the text, in some cases so close they blend with the letters.
Describe the solution you'd like
A configurable padding/separator option would be nice, either an integer to set the number of spaces, or just a straight up string of characters.
Describe alternatives you've considered
I did find a function that pads icons with one space in utils.lua, but while altering it to print 2+ spaces does provide the desired effect in some pickers (e.g. builtin.find_files), others (e.g. builtin.buffers) are not affected for whatever reason, and I couldn't figure out why.
Additional context
The text was updated successfully, but these errors were encountered:
This would be such a tedious option to implement for such a niche font preference issue. I can't see us implementing this, at least in the near future.
It'd probably be easier to set up override icons for nvim-web-devicons with extra whitespace appended. Might be possible to do this programmatically.
Is your feature request related to a problem? Please describe.
With narrow fonts (e.g. Iosevka), devicons are located too close to the text, in some cases so close they blend with the letters.
Describe the solution you'd like
A configurable padding/separator option would be nice, either an integer to set the number of spaces, or just a straight up string of characters.
Describe alternatives you've considered
I did find a function that pads icons with one space in utils.lua, but while altering it to print 2+ spaces does provide the desired effect in some pickers (e.g.
builtin.find_files
), others (e.g.builtin.buffers
) are not affected for whatever reason, and I couldn't figure out why.Additional context
The text was updated successfully, but these errors were encountered: