GNU nano - Bugs: bug #44908, [Request] enhance the precision of...
You are not allowed to post comments on this tracker with your current authentication level.
bug #44908: [Request] enhance the precision of which signal was received
Submitter: | Sworddragon <sworddragon> | ||
Submitted: | Thu 23 Apr 2015 01:55:29 PM UTC | ||
Severity: | 1 - Wish | Status: | Wont Fix |
Assigned to: | None | Open/Closed: | Closed |
Jump to the original submission
Wed 29 Apr 2015 08:14:39 PM UTC, comment #6: |
Sworddragon <sworddragon> |
Wed 29 Apr 2015 07:47:05 AM UTC, comment #5: It seems you haven't understood the argument for closing: without an actual use case where it is important to know whether it was HUP or TERM that terminated nano, I will not make the change nor accept a patch. |
Benno Schulenberg <bens> |
Tue 28 Apr 2015 08:30:11 PM UTC, comment #4: Why to close this ticket then? The request would make this more clear so I think it would be better to give it a low priority instead. This allows contributors to see what they can enhance so somebody would then maybe provide a patch for this in the future. |
Sworddragon <sworddragon> |
Tue 28 Apr 2015 07:24:59 PM UTC, comment #3: Without a clear case of where this would be useful... |
Benno Schulenberg <bens> |
Fri 24 Apr 2015 06:22:18 PM UTC, comment #2: I have just noticed this on using nano and thought it could be a nice enhancement. |
Sworddragon <sworddragon> |
Fri 24 Apr 2015 07:40:04 AM UTC, comment #1: Can you give me a scenario where it is important for you to know exactly which signal was received? |
Benno Schulenberg <bens> |
Thu 23 Apr 2015 01:55:29 PM UTC, original submission:
I'm using nano 2.2.6 and on sending a SIGTERM I'm getting the output "Received SIGHUP or SIGTERM". Maybe the precision which signal got received could be enhanced here. |
Sworddragon <sworddragon> |
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 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2015-04-28 | bens | Status | None | Wont Fix | |
Open/Closed | Open | Closed | |||
2015-04-24 | bens | Severity | 3 - Normal | 1 - Wish | |
Summary | Enhancing the precision of which signal got received | [Request] enhance the precision of which signal was received |
Powered by Savane 3.13-4448.
Corresponding source code
It's an enhancement that wouldn't hurt - it reminds me of trivial options in any other application. Also not accepting a potential patch seems to be strange - or would such an enhancement make somehow troubles?