Why does Mutt's (more specifically, Neomutt's) “quit” command change depending on which screen I'm on?











up vote
0
down vote

favorite












If I'm viewing an HTML-based email, the steps to view it are:



Inbox: select email, press [Enter]
Email: text/html is unsupported, press [v]
Email: viewing attachments, select and press [Enter]
Now viewing HTML


But now that I'm viewing the HTML, to get back out to my inbox and then quit neomutt, the key sequence is:



[i] -> [q] -> [i] -> [q]
| | | ^ to exit mutt
| | ^ to exit the email itself
| ^ to exit the attachment list
^ to exit the attachment


Why does it switch back and forth? I've read some tutorials on replacing the keybindings, but I'm more interested in understanding why both 'i' and 'q' seem to map to the same function, depending on which screen you're viewing?










share|improve this question
























  • By default, q should always work, but mail / attachment view (i.e. the pager set of bindings) additionally has i and x bound to <exit>. The manual does not mention these aliases, only the q bindings, so I'd suspect they are there for historical reasons.
    – crater2150
    Nov 20 at 12:37















up vote
0
down vote

favorite












If I'm viewing an HTML-based email, the steps to view it are:



Inbox: select email, press [Enter]
Email: text/html is unsupported, press [v]
Email: viewing attachments, select and press [Enter]
Now viewing HTML


But now that I'm viewing the HTML, to get back out to my inbox and then quit neomutt, the key sequence is:



[i] -> [q] -> [i] -> [q]
| | | ^ to exit mutt
| | ^ to exit the email itself
| ^ to exit the attachment list
^ to exit the attachment


Why does it switch back and forth? I've read some tutorials on replacing the keybindings, but I'm more interested in understanding why both 'i' and 'q' seem to map to the same function, depending on which screen you're viewing?










share|improve this question
























  • By default, q should always work, but mail / attachment view (i.e. the pager set of bindings) additionally has i and x bound to <exit>. The manual does not mention these aliases, only the q bindings, so I'd suspect they are there for historical reasons.
    – crater2150
    Nov 20 at 12:37













up vote
0
down vote

favorite









up vote
0
down vote

favorite











If I'm viewing an HTML-based email, the steps to view it are:



Inbox: select email, press [Enter]
Email: text/html is unsupported, press [v]
Email: viewing attachments, select and press [Enter]
Now viewing HTML


But now that I'm viewing the HTML, to get back out to my inbox and then quit neomutt, the key sequence is:



[i] -> [q] -> [i] -> [q]
| | | ^ to exit mutt
| | ^ to exit the email itself
| ^ to exit the attachment list
^ to exit the attachment


Why does it switch back and forth? I've read some tutorials on replacing the keybindings, but I'm more interested in understanding why both 'i' and 'q' seem to map to the same function, depending on which screen you're viewing?










share|improve this question















If I'm viewing an HTML-based email, the steps to view it are:



Inbox: select email, press [Enter]
Email: text/html is unsupported, press [v]
Email: viewing attachments, select and press [Enter]
Now viewing HTML


But now that I'm viewing the HTML, to get back out to my inbox and then quit neomutt, the key sequence is:



[i] -> [q] -> [i] -> [q]
| | | ^ to exit mutt
| | ^ to exit the email itself
| ^ to exit the attachment list
^ to exit the attachment


Why does it switch back and forth? I've read some tutorials on replacing the keybindings, but I'm more interested in understanding why both 'i' and 'q' seem to map to the same function, depending on which screen you're viewing?







keyboard-shortcuts mutt






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 at 11:45

























asked Nov 20 at 11:37









Craig Otis

1186




1186












  • By default, q should always work, but mail / attachment view (i.e. the pager set of bindings) additionally has i and x bound to <exit>. The manual does not mention these aliases, only the q bindings, so I'd suspect they are there for historical reasons.
    – crater2150
    Nov 20 at 12:37


















  • By default, q should always work, but mail / attachment view (i.e. the pager set of bindings) additionally has i and x bound to <exit>. The manual does not mention these aliases, only the q bindings, so I'd suspect they are there for historical reasons.
    – crater2150
    Nov 20 at 12:37
















By default, q should always work, but mail / attachment view (i.e. the pager set of bindings) additionally has i and x bound to <exit>. The manual does not mention these aliases, only the q bindings, so I'd suspect they are there for historical reasons.
– crater2150
Nov 20 at 12:37




By default, q should always work, but mail / attachment view (i.e. the pager set of bindings) additionally has i and x bound to <exit>. The manual does not mention these aliases, only the q bindings, so I'd suspect they are there for historical reasons.
– crater2150
Nov 20 at 12:37















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f482950%2fwhy-does-mutts-more-specifically-neomutts-quit-command-change-depending-o%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f482950%2fwhy-does-mutts-more-specifically-neomutts-quit-command-change-depending-o%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Morgemoulin

Scott Moir

Souastre