+++ This bug was initially created as a clone of Bug #1219923 +++
Description of problem (quoting cloned bug description):
This was reported to upstream:
An user reported a problem, that apparently happens for quite
The user reports that interrupting this command:
eval sleep 10
would keep history in tcsh-6.14.00, but not in tcsh-6.18.01.
Actually, I believe the history not being logged is due to
and the problem is another, as the inconsistent state
happens in all tcsh versions. Basically, when doeval()
calls process(), process() does not leave, so one needs
to ^D twice to get back to the consistent state.
The attached patch correct this condition, and based
on code I could read is correct, but I would like some
feedback on it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run 'tcsh'.
2. run command:
> eval sleep 10
3. press <Ctrl-C> during that time
4. press <Ctrl-D> to close the terminal
You have to press <Ctrl-D> once again to actually exit the terminal.
The 'tcsh' exits normally after first pressing of <Ctrl-D>.
--- Additional comment from Paulo Andrade on 2015-05-09 08:59:43 EDT ---
Update patch, as initially proposed patch would
break the shell (was exiting if pressing ^C),
while the idea was to just leave the inconsistent
state after ^C during eval.
--- Additional comment from Fridolín Pokorný on 2015-05-13 08:31:13 EDT ---
Thanks for the report and provided patch!
It looks OK to me and it sounds reasonable to merge this patch, no fail noted in upstream testsuite as well.
--- Additional comment from David Kaspar [Dee'Kej] on 2015-10-20 07:12:21 EDT ---
Here is the mailing list conversation mentioned in the comment #0:
--- Additional comment from David Kaspar [Dee'Kej] on 2015-10-20 07:22:03 EDT ---
The conversation in the mailing list might be misleading to somebody - it might look like the patch was not accepted:
> And removed. This breaks the shell completely; a ^C makes it exit.
However, will small tweak, the patch was accepted by the upstream:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.