GNU nano - Bugs: bug #57953, [Wish] use the top-right corner...
You are not allowed to post comments on this tracker with your current authentication level.
bug #57953: [Wish] use the top-right corner for state information
Submitter: | Seb <seb5903> | ||
Submitted: | Wed 04 Mar 2020 07:55:18 PM UTC | ||
Severity: | 1 - Wish | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Jump to the original submission
Thu 08 Oct 2020 08:54:11 AM UTC, comment #15: |
Benno Schulenberg <bens>![]() ![]() |
Wed 23 Sep 2020 06:26:32 PM UTC, comment #14: Fixed in git, commit d679bbc8. (Two subsequent commits clean things up and add documentation.) |
Benno Schulenberg <bens>![]() ![]() |
Sun 20 Sep 2020 03:20:21 PM UTC, comment #13: You could consider breaking convention and use # instead of *, way more visible, you'd only need 1.
|
Peter Passchier <pepa65> |
Sun 20 Sep 2020 02:27:22 PM UTC, comment #12: If you use a patch and you like it (or don't like it), please give feedback on the mailing list. If nobody says anything, how am I supposed to know what people think?
|
Benno Schulenberg <bens>![]() ![]() |
Sun 20 Sep 2020 09:19:12 AM UTC, comment #11: To me, really useful, so really great. I don't think you need 2 asterisks, one should be enough. (When I was seeing it, I thought, what does TWO asterisks mean?) Having 1 is a well established convention.
|
Peter Passchier <pepa65> |
Sun 10 May 2020 03:25:01 PM UTC, comment #10: A first implementation of the feature was posted by Marco to the devel list: https://lists.gnu.org/archive/html/nano-devel/2020-04/msg00053.html. If you have tried the patch, please post your experiences to that thread. |
Benno Schulenberg <bens>![]() ![]() |
Sun 10 May 2020 10:30:57 AM UTC, comment #9: If this feature was available, I would certainly turn the "show the flag" on for Modified, Macro-recording, Auto-indent, and Mark-set. I never use Hard-wrapping, so I just would not turn that on.
|
Peter Passchier <pepa65> |
Sun 19 Apr 2020 09:16:29 AM UTC, comment #8: I am not forcing anything on anyone. If people don't like how the flags work, then they shouldn't use the option that switches them on. And stop telling what I should do or not do! I have no interest in making a patch -- I wouldn't use it. Also, the patch wouldn't use lowercase to indicate an option is off, because then the contrast would be far too low: you would have to look closely to see whether an option is on or off. |
Benno Schulenberg <bens>![]() ![]() |
Sat 18 Apr 2020 11:59:53 AM UTC, comment #7: These are interesting points.
|
Seb <seb5903> |
Fri 17 Apr 2020 11:14:33 PM UTC, comment #6: You are forcing clutter up there for anyone who doesn't use nano the way you use nano. There should at least be an option to hide the flags if same as nanorc. Make a patch that always displays a letter for each flag, uppercase if enabled and lowercase if not. Try it out for a while and see if having that constant clutter makes it useful.
|
Brand Huntsman <brand> |
Fri 17 Apr 2020 03:32:29 PM UTC, comment #5: When the content of a nanorc file influences when what is shown in the top-right corner, and you don't know or don't remember what is in nanorc, then you won't know whether the absence of an A and H means autoindent and hardwrap are off or on. When I look at an unknown nano and I see some letter in the top-right corner, but not an H, then I want to be sure that hardwrapping is off.
|
Benno Schulenberg <bens>![]() ![]() |
Thu 16 Apr 2020 10:01:06 PM UTC, comment #4: It would need to know the initial normal state (nanorc but not command line flags) of some flags such as autoindent and hardwrap. If the normal state is always enabled, it could use a lowercase letter when disabled. Otherwise those who always use hardwrap would always have an "H" up there and becomes useless clutter that also makes the other letters less visible.
|
Brand Huntsman <brand> |
Thu 05 Mar 2020 12:05:40 PM UTC, comment #3: It is possible for the entire selected region to be out of view. For example: run 'nano +1 README', type ^6, and then M-= a few times (that scrolls the screen while keeping the cursor on the top row of the edit window). Now go and make a cup of tea, then come back. Question: is the mark on, or not? :) |
Benno Schulenberg <bens>![]() ![]() |
Thu 05 Mar 2020 11:04:10 AM UTC, comment #2: Agreed for an option.
|
Seb <seb5903> |
Thu 05 Mar 2020 10:54:58 AM UTC, comment #1: (Hmm. I didn't get an email about this item. Normally Savannah sends me an email when a new item is posted.)
|
Benno Schulenberg <bens>![]() ![]() |
Wed 04 Mar 2020 07:55:18 PM UTC, original submission:
When I edit a file, I switch on an off auto-indent and hardwrap depending on the current content. But I often wonder whether either on these switches is on or off.
|
Seb <seb5903> |
No files currently attached
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 7 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2020-10-08 | bens | Open/Closed | Open | ![]() |
Closed |
2020-09-23 | bens | Status | In Progress | ![]() |
Fixed |
2020-09-19 | bens | Status | None | ![]() |
In Progress |
Assigned to | None | ![]() |
bens | ||
2020-03-05 | bens | Severity | 3 - Normal | ![]() |
1 - Wish |
Summary | [wish] Use top right space for state information | ![]() |
[Wish] use the top-right corner for state information | ||
2020-03-04 | seb5903 | Carbon-Copy | - | ![]() |
Added -email is unavailable- |
Option --stateflags and 'set stateflags' was released in version 5.3.