feat: add config option editor.statusline.unobtrusive
to make statusline not block the last line of text
#12020
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.
per popular request: How to disable / remove statusline? #7934
This PR adds a new
editor.statusline.unobtrusive
(boolean) optionPreviously, the statusline would always block one line of the screen. But now, if this option is set then the statusline elements will be overlaid on top of the bottom line of text without blocking that line
Showcase
With the following config, the text on line 23 is not visible.
And setting
unobtrusive = true
makes the text on line 23 visible.Notes
Since people use their text editors with other software like multiplexers, having an entire line blocking the text isn't good for integrations.
With this config, you can hide all of the status line's elements:
Most notable changes are in these files:
render
method inhelix-term/src/ui/statusline.rs:52
inner_area
andinner_height
methods inhelix-view/src/view.rs:193
Most other changes were just passing the
unobtrusive_statusline
argument