GNU nano - Bugs: bug #63114, when piping text to a command...
You are not allowed to post comments on this tracker with your current authentication level.
bug #63114: when piping text to a command fails, there is no error message
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Tue 27 Sep 2022 02:22:25 PM UTC | ||
Severity: | 3 - Normal | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Fri 07 Oct 2022 07:48:09 AM UTC, comment #3: |
Benno Schulenberg <bens> |
Tue 04 Oct 2022 02:39:23 PM UTC, comment #2: Proposed patch is attached. |
Benno Schulenberg <bens> |
Wed 28 Sep 2022 10:07:23 AM UTC, comment #1: For consistent reproduction, the recipe needs a "+1":
(The +1 can be dropped when bug #63120 has been fixed.) |
Benno Schulenberg <bens> |
Tue 27 Sep 2022 02:22:25 PM UTC, original submission:
To see what I mean, add an 'exit(8)' at the beginning of send_data(), compile, and then run 'src/nano README'.
|
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 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2022-11-16 | bens | Open/Closed | Open | Closed | |
2022-10-07 | bens | Status | In Progress | Fixed | |
2022-10-04 | bens | Attached File | - | Added 0001-files-improve-the-error-handling-when-executing-an-e.patch, #53788 | |
Status | None | In Progress | |||
2022-09-27 | bens | Summary | when piping text out to a command fails, there is no error message | when piping text to a command fails, there is no error message |
Powered by Savane 3.13-d3ae.
Corresponding source code
Fixed in git, commit 19c8cea8, by checking the exit status of both the command process and the data-sending process. (The latter probably never fails, but... just in case.)
(There is be a small chance that a failed command process did not result in an error message from the shell, and thus, if the line before the cursor contains a colon followed by a space, nano will print the text after that as the error message, which would be majorly confusing. I will have to experiment with that, to see if this can occur, and for that, the code has to be in the mainline.)