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
Configurable EOL offset #104
Comments
Hi! I never considered this since we had a single template until recently, but I see how this could be useful.
Are you suggesting changing the behavior with the introduction of |
Yep, I figured it would be something like this 😄 👍.
Not necessarily in a breaking way, only that Or thinking about this some more, just always use Something like:
|
Currently the EOL offset for the message template or not committed template requires prepending with spaces, additionally the
virtual_text_column
will default to the EOL when the line is longer than this setting.However, the need to prepend spaces is both visually messy and adds a (small, but not invisible) layer of maintenance cost now that there are multiple templates. It also requires overriding the default templates even if the only thing a user wants to configure is the offset.
Did you consider adding something like an
eol_offset
config to allow something likeSo that all messages are consistently offset by 5 cols from the end of the line and messages.
The text was updated successfully, but these errors were encountered: