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
The default value for statusformatl is: $(filename) $(modified)($(line),$(col)) $(status.paste)| ft:$(opt:filetype) | $(opt:fileformat) | $(opt:encoding)
This default relies on both the statusline Go file and the Lua plugin. Additionally, both files contain values or logic that aren't actually used in the default configuration.
To simplify things, wouldn't it make sense to gather everything into one place?
If so, we could:
Option 1: Move all the logic to the plugin.
Option 2: Move all the logic to the Go statusline file and remove the plugin entirely.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I've noticed that the statusformatl options are currently split across two places:
Statusline file (Go)
Status built-in plugin (Lua)
The default value for statusformatl is:
$(filename) $(modified)($(line),$(col)) $(status.paste)| ft:$(opt:filetype) | $(opt:fileformat) | $(opt:encoding)
This default relies on both the statusline Go file and the Lua plugin. Additionally, both files contain values or logic that aren't actually used in the default configuration.
To simplify things, wouldn't it make sense to gather everything into one place?
If so, we could:
Any thoughts?
Beta Was this translation helpful? Give feedback.
All reactions