GNU nano - Bugs: bug #50362, warning delays make nano unusable...
You are not allowed to post comments on this tracker with your current authentication level.
bug #50362: warning delays make nano unusable in some scenarios
Submitter: | Mike Frysinger <vapier> | ||
Submitted: | Mon 20 Feb 2017 06:36:09 PM UTC | ||
Severity: | 3 - Normal | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Jump to the original submission
Wed 01 Mar 2017 09:11:47 PM UTC, comment #6: |
Mike Frysinger <vapier> |
Wed 01 Mar 2017 08:24:14 PM UTC, comment #5: Hmm... What do you mean with "flipping between files"? Do you get warnings and delays when you use Alt+< and Alt+> to switch between buffers? Or when you use ^X to close one buffer and thus are switched to the next?
|
Benno Schulenberg <bens> |
Wed 01 Mar 2017 05:12:33 PM UTC, comment #4: while the new version improves things, i'm not sure it's enough at least for my usage. i still find the delay when flipping between files annoying.
|
Mike Frysinger <vapier> |
Fri 24 Feb 2017 10:40:12 AM UTC, comment #3: Fix has been released in 2.7.5. |
Benno Schulenberg <bens> |
Wed 22 Feb 2017 10:40:03 AM UTC, comment #2: Problem is avoided in git, 23c3fd9b. Thanks for reporting. |
Benno Schulenberg <bens> |
Tue 21 Feb 2017 11:56:56 AM UTC, comment #1: Indeed, it is silly to bury the user in an endless series of warnings. Showing just a handful and then skipping all the rest should be enough.
|
Benno Schulenberg <bens> |
Mon 20 Feb 2017 06:36:09 PM UTC, original submission:
nano was changed to delay after showing a warning. this is a problem if you pull up a bunch of files that are read-only specifically so you can pull text out of them.
|
Mike Frysinger <vapier> |
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 |
---|---|---|---|---|---|
2017-03-01 | bens | Attached File | - | Added allow-specifying-the-maximum-number-of-wranings.patch, #39872 | |
2017-02-24 | bens | Open/Closed | Open | Closed | |
2017-02-22 | bens | Status | In Progress | Fixed | |
2017-02-21 | bens | Attached File | - | Added stop-delaying-when-there-are-many-alerts.patch, #39804 | |
Status | None | In Progress | |||
Assigned to | None | bens |
Powered by Savane 3.13-4448.
Corresponding source code
i'll be working on one file i have write access to, but i want to pull content out of ones i don't
$ nano /usr/lib/...some python modules... ./test.py
i get hit by the delays while nano warns me that i can't write to those system files
then i remember i need to pull some more modules up, so i close all the existing files (hold ctrl+x), then reload my nano command line and add a few more system modules. then i get hit by the delays again.
i could manually load them one-by-one from inside nano, but that's a pain when i want to use *.py, and that won't be remembered in my command line history.
i already know i can't write to root-owned files living in system paths ... i don't need to be told that over and over :).
that patch seems to work for my situation.