On 2010-03-11, Mutt <[email protected]> wrote: > #3391: g key feedback the same as r > ---------------------+------------------------------------------------------ > Reporter: jidanni | Owner: mutt-dev > Type: defect | Status: new > Priority: trivial | Milestone: > Component: mutt | Version: 1.5.20 > Keywords: | > ---------------------+------------------------------------------------------ > > Comment(by jidanni): > > The new user doesn't really care about being asked. He just wants to see > some indication that this isn't just the same as "r". So something should > appear at that point showing that mutt knows he hit g and not r.
I don't understand your objection to 'askcc'. Have you tried it? Without 'askcc' set, the user types r or g and sees the To: list. He verifies that it's correct and hits Enter. He next sees the Subject: line. He verifies that it's correct or changes it to suit, and hits Enter again. He is now in his editor. With 'askcc' set, the user types r or g and sees the To: list as above. After hitting Enter, he sees the Cc: list. If he had typed r, this is empty. If he had typed g and there were other addressees in the original message, this has the list of the other addressees. If that's all he needs to know, he hits Enter again and sees the Subject: line as above. In practice, this means that there is one more Enter to hit between typing r or g (or any other key to begin a message) and the point at which the user begins editing the message. The user gets quick confirmation of who is in the To: and Cc: lists. If the Cc: list is wrong because the user hit the wrong key to start, he types Ctrl-G and tries again. Setting 'askcc' and being shown the Cc: list provides the user with confirmation that the message is being addressed as desired and in a manner that's timely and consistent with mutt's other feedback. Regards, Gary
