Version-Release number of selected component (if applicable): mutt-1.4.2.2-3.0.2.el5.x86_64 How reproducible: 100% Steps to Reproduce: 1. run mutt 2. press / - mutt displays the "Search for:" prompt. 3. press Ctrl-C Actual results: nothing happens. Only after the next key is pressed, mutt displays the Ctrl-C question: "Exit Mutt? ([yes]/no):" when "no" is chosen, mutt remains in the search mode, but the "Search for:" prompt is not redrawn, leaving the user confused on what to do next. Expected results: mutt should display the "Exit Mutt?" question immediately after Ctrl-C is pressed. When "no" is chosen, the search string and prompt should be redrawn, or mutt should leave the search mode altogether (which is what mutt-1.5 does). Additional info: mutt-1.5.14-4.fc7 on Fedora system does not have this problem. vanilla mutt-1.5.16 (from mutt.org), compiled with "./configure --prefix=/usr/local; make; make install" on RHEL 5 also does not have this problem. I have tested this only on x86_64 systems (both RHEL 5 and Fedora 7), but since I don't think an architecture-specific bug is likely, I am leaving the Platform: tag set to "All".
Created attachment 214881 [details] upstream patch to allow interrupt in getch
mutt-1.4.2.2-3.0.2.el5.x86_64 + the patch from comment #1 works for me. Thanks!
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. This request will be reviewed for a future Red Hat Enterprise Linux release.
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?".
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. http://rhn.redhat.com/errata/RHBA-2012-1143.html