GNU nano - Bugs: bug #64019, with --zero, the filename flashes...
You are not allowed to post comments on this tracker with your current authentication level.
bug #64019: with --zero, the filename flashes by when switching between buffers
Submitter: | Alan Cristhian Ruiz <alancristhian> | ||
Submitted: | Sun 09 Apr 2023 08:52:21 PM UTC | ||
Severity: | 2 - Minor | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Open |
Jump to the original submission
Wed 12 Apr 2023 01:55:40 PM UTC, comment #7: |
Alan Cristhian Ruiz <alancristhian> |
Wed 12 Apr 2023 08:25:00 AM UTC, comment #6: Indeed, what to show with --zero, and what not, is a matter of taste. For me the criterium was: anything that I don't need to see should be hidden. That's the idea of --zero. If I want to see which file I'm in, I quickly toggle M-Z twice -- I use --minibar, so normally this does not make the text in the window move and is thus not distracting.
|
Benno Schulenberg <bens>![]() ![]() |
Tue 11 Apr 2023 04:10:32 PM UTC, comment #5: I actually expected to see the filename. But I understand that the choose of what should be displayed or not is a matter of taste. That could be a long discussion.
|
Alan Cristhian Ruiz <alancristhian> |
Tue 11 Apr 2023 10:00:37 AM UTC, comment #4: Attached patch will prevent the flashing. (If you don't want your email address in the commit message, I can remove it.) |
Benno Schulenberg <bens>![]() ![]() |
Tue 11 Apr 2023 09:42:48 AM UTC, comment #3: Okay, I see what you mean. But the idea of --zero is to give only important/necessary feedback and to hide/suppress the chattiness. So the problem is not that the filename is shown for too short a time but that it is visible at all. I can fix that for this particular case, but nano writes messages to the status bar in various places and relies on the screen refresh quickly overwriting unimportant ones when --zero is active. You can probably see a flashing message when you hold down Alt+A long enough, or when you place two anchors and then hold down Alt+PgDn. I am not going to fix those, because there are too many of them. And I cannot fix it by just suppressing all messages of the HUSH level because some of these I do want to see even with --zero (for example: when opening a huge file, I want to see the "Reading..." feedback). |
Benno Schulenberg <bens>![]() ![]() |
Mon 10 Apr 2023 06:58:13 PM UTC, comment #2: Nano 7.2, the one that comes by default on the latest Debian 12.0 bookworm build.
3. Press and hold Alt-RightArrow. It will quickly switch between buffers.
|
Alan Cristhian Ruiz <alancristhian> |
Mon 10 Apr 2023 08:09:47 AM UTC, comment #1: Cannot reproduce. For me, in zero-interface mode, the filename is not displayed at all, so I'm puzzled where you shortly see the filename. Please provide a recipe where you use only command-line options. Something like this:
|
Benno Schulenberg <bens>![]() ![]() |
Sun 09 Apr 2023 08:52:21 PM UTC, original submission:
Filename is not displayed long enough after changing buffers in zero interface mode.
|
Alan Cristhian Ruiz <alancristhian> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 8 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2023-04-12 | bens | Status | Ready For Test | ![]() |
Fixed |
2023-04-11 | bens | Attached File | - | ![]() |
Added 0001-files-suppress-filename-and-number-of-lines-when-zer.patch, #54598 |
Status | Confirmed | ![]() |
Ready For Test | ||
Assigned to | None | ![]() |
bens | ||
2023-04-11 | bens | Severity | 3 - Normal | ![]() |
2 - Minor |
Status | Need Info | ![]() |
Confirmed | ||
Summary | Filename is not displayed long enough after changing buffers in zero interface mode | ![]() |
with --zero, the filename flashes by when switching between buffers | ||
2023-04-10 | bens | Status | None | ![]() |
Need Info |
Yes is mine, but i threw there other unrelated stuff. Maybe i should only keep the nano related code.