Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 105808 - missing key bindings in mutt
missing key bindings in mutt
Status: CLOSED DUPLICATE of bug 105781
Product: Fedora
Classification: Fedora
Component: mutt (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 2003-09-27 17:51 EDT by Graydon Saunders
Modified: 2014-03-16 22:39 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:58:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Graydon Saunders 2003-09-27 17:51:41 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.76 (Linux 2.4.22-1.2061.nptl i686; U) Opera 7.11  [en]

Description of problem:
Default mutt keybindings have <end> as the 'jump to end of message' command.

This works with mutt-1.4-10; it doesn't work with 1.4.1-4.

Instead, I get "Key is not bound.  Press '?' for help."

If I do that, I find in the help:

<End>       bottom                 jump to the bottom of the message

The binding for <Home> ('jump to top of the message') also appears to be 

This is with the default /etc/Muttrc as well as with my lightly customized one.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. open a long message in mutt
2. press <end>

Actual Results:  Error message - Key is not bound.  Press '?' for help.

Expected Results:  Jumping to the end of the message.

Additional info:
Comment 1 Bill Nottingham 2003-09-29 00:06:35 EDT

*** This bug has been marked as a duplicate of 105781 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:58:48 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.