GNU nano - Bugs: bug #54754, when linter shows "first/last...
You are not allowed to post comments on this tracker with your current authentication level.
bug #54754: when linter shows "first/last message", there is no direct way to show message again
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Sat 29 Sep 2018 07:38:45 AM UTC | ||
Severity: | 2 - Minor | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Jump to the original submission
Mon 22 Oct 2018 06:45:34 PM UTC, comment #7: |
Benno Schulenberg <bens> |
Mon 22 Oct 2018 01:29:51 AM UTC, comment #6: That is better than the other patches, except it has a bug that needs to be fixed.
|
Brand Huntsman <brand> |
Sun 21 Oct 2018 04:02:46 PM UTC, comment #5: Neither of the patches works for me. (Although I don't understand why the one from Brand doesn't work.) So I have pushed a different change, mostly similar to what David posted: commit b8c51329. |
Benno Schulenberg <bens> |
Thu 18 Oct 2018 09:32:01 PM UTC, comment #4: extendsyntax c linter "gcc -fsyntax-only"
|
Brand Huntsman <brand> |
Thu 18 Oct 2018 06:53:10 PM UTC, comment #3: Yes, I have gcc. As I said before, I have no way to test it without installing a linter and programming language that I don't use. My intent was to just display the "first/last line" message, delay a bit, and then display the message from before; I forgot that warn_and_shortly_pause() does more than delay. I suppose I shouldn't have bothered with my patch here, then. |
David Lawrence Ramsey <dolorous> |
Thu 18 Oct 2018 01:42:19 PM UTC, comment #2: Do you have gcc?
|
Brand Huntsman <brand> |
Wed 17 Oct 2018 05:13:45 PM UTC, comment #1: Would something like the attached work?
|
David Lawrence Ramsey <dolorous> |
Sat 29 Sep 2018 07:38:45 AM UTC, original submission:
When using the linter [surprisingly it is quite hard to get used to M-B for accessing the linter], and with ^Y or ^V you tried to go beyond the first or last message, the helpful report from the linter that this is the first or last message stays on screen and "hides" the actual linting message. When there are multiple messages, it is easy to see the first/last message again by jumping one message in the other direction and then jumping back, but when there is just one message this is impossible: the status bar would alternate between "This is the first message" and "This is the last message". The pnly way to get the message back then would be to exit from the linter and invoke it again.
|
Benno Schulenberg <bens> |
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 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2018-11-12 | bens | Open/Closed | Open | Closed | |
2018-10-22 | brand | Attached File | - | Added 0001-linter-throttle-first-last-message-on-key-repeat.patch, #45255 | |
2018-10-21 | bens | Status | None | Fixed | |
Assigned to | None | bens | |||
2018-10-18 | brand | Attached File | - | Added 0001-linter-re-show-current-message-on-prev-next-keypress.patch, #45235 | |
2018-10-17 | dolorous | Attached File | - | Added 0001-linter-after-indicating-first-last-message-display-i.patch, #45224 |
Powered by Savane 3.13-f8d8.
Corresponding source code
I was going to say that this is too small an issue to bother with, but I like the improved behavior, and it costs just a few lines, so I've applied and pushed the patch, commit 71de0b9e. Thanks.