Fix indentation and tab/space indentation representation in Neovim #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In order to easily distinguish between tab- and space-based indentation, this sets the `tab` value in `listchars` to show a › after a vertical line.
Because vim-sleuth will dynamically change the values of `tabstop` and `shiftwidth` based on context cues and config files, a single value for `lcs-multispace` leads to unexpected behavior where multiple vertical lines may be shown for each level of indentation. This implements autocmds to adjust the value of `lcs-multispace` whenever `shiftwidth` and/or `tabstop` change, so that there will always be a single vertical line per level of indentation, as detected by vim-sleuth.
vicnett
force-pushed
the
fix-vim-indentation-listchars
branch
from
ab0a8b4 to
70bedb7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
lcs-tabandlcs-leadmultispaceshow different secondary characters to visually differentiate between space- and tab-based indentation.lcs-leadmultispaceautomatically adapt totabstopand/orshiftwidthchanges.vim/to use two-space indentation.Why
I wanted two-space indentation in Lua files all along, and I thought I had achieved that using
styluabut I accidentally made them all use tabs, and I didn't realize because my "visual" Neovim config was set to show leading tabs and leading spaces the same way.While working on solving this, I realized that the length of
lcs-leadmultispaceneeds to match the length of space-based indentation for it to "line up" visually. Since I use a vertical line character to indicate indentation, thelcs-leadmultispacevalue definitely needs to keep up with indentation so that the line will line up, or it will defeat the purpose.I found and adapted some
autocmdcode that will dynamically changelcs-leadmultispaceevery time eithertabstoporshiftwidthchanges, which in turn are kept dynamically in sync with local indentation byvim-sleuth.Testing
lcs-leadmultispacecorrectly follows changes in indentation, resulting in expected "vertical indentation guide line" behavior.