Skip to content
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

[Feature request] Use the last line as part of editor space #3630

Open
pachpict opened this issue Jan 23, 2025 · 6 comments
Open

[Feature request] Use the last line as part of editor space #3630

pachpict opened this issue Jan 23, 2025 · 6 comments

Comments

@pachpict
Copy link

Issue

Currently you can turn off the status line but in this case the last line is simply blank during editing (until you, for example, save the file) and therefore not used for editing.

Feature request

Allow for the last line be be part of the editing screen space, except it covered over by, e.g. the save file message when that comes up.

Currently it looks like this (in a file containing the string "q\nw\ne\nr\nt\ny\nu\ni\no", ruler on) during editing:

1 q
2 w
3 e
4 r
5 t
6 y
7 u
8 i

... and when being saved...

1 q
2 w
3 e
4 r
5 t
6 y
7 u
8 i
Filename: 

I am proposing an option that makes it look like this:

1 q
2 w
3 e
4 r
5 t
6 y
7 u
8 i
9 o

... and when being saved...

1 q
2 w
3 e
4 r
5 t
6 y
7 u
8 i
Filename: 

Reason for the request

We are on a 9 line multiline Braille terminal with 9 lines. Space is precious, but even more importantly a standard Braille file is 27 lines long, meaning a 3rd of it will fit on 9 lines. We have many Braille files which have been specifically formatted to 9 lines for our display, but currently are not able to meaningfully retain formatting when editing or viewing those pre-formatted Braille files.

Environment

Tested on v2.0.13 on Canute Console running Raspberry Pi OS and same version on Linux Mint x64.

@niten94
Copy link
Contributor

niten94 commented Jan 25, 2025

I do not know if this explanation makes sense with a Braille terminal, but using the whole screen as editor space is already possible. With default settings, the 1st last line is the infobar and 2nd is the status line. There is usually nothing displayed in the infobar, but it can be hidden when disabling infobar option.

@dmaluka
Copy link
Collaborator

dmaluka commented Jan 25, 2025

Right, I think the requested behavior is already possible, by turning off both statusline and infobar options.

@pachpict does that work for you?

@pachpict
Copy link
Author

Thank you both and apologies for misreading or missing the existing options. I am not in a position to test it for the next few days but the Braille display mirrors the exact same lines as the visual terminal (up to nine) so there's no reason it shouldn't work.

@usfbih8u
Copy link
Contributor

usfbih8u commented Jan 26, 2025

The last line will be empty and never used, even with both disabled (at least in 2.0.14).

You also lose the capability of seeing Infobar messages. And that is a significant trade-off, at least for me.

@dmaluka
Copy link
Collaborator

dmaluka commented Jan 26, 2025

The last line will be empty and never used, even with both disabled (at least in 2.0.14).

Are you sure? Perhaps what you are seeing is the following phenomenon: if the height of a single line is e.g. 10 pixels while the height of the terminal window is not a multiple of 10, e.g. if it is 508 pixels, the terminal can display only 50 lines, plus it also has a "trimmed" line of 8 pixels at the bottom, which is always empty and unused, in micro or any other application, since from micro's or any other application's perspective this line doesn't exist.

@usfbih8u
Copy link
Contributor

usfbih8u commented Jan 26, 2025

You are right! When I tried it, with and without tmux, the last line did not even put the number in the last line. Maybe I re-enabled the infobar by mistake(?). I can't reproduce it, so it has to be a mistake on my part.

Edit:

I know what happened. There was a conflict with a plugin that I use to include multiple color schemes at runtime. It "hijacks" the settings.json file, and I keep forgetting about this, the changes were not applied correctly or were recovered between tests.

So it does not have anything to do with Micro.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants