On Thu, May 09, 2024 at 05:59:39PM +0200, Dennis Preiser wrote: > On Thu, May 09, 2024 at 04:24:56PM +0100, Chris Green wrote: > > I have the following in muttrc so that hitting 'Enter' (the CR key) on > > the keyboard sends an E-Mail after composing it:- > > > > bind compose \n send-message # rather than 'y' > > > > This works as intended on the old system but not on the new system, it > > would seem that mutt sees the 'Enter' key as CR (0x0d) on the new > > system whereas on the old system it sees it as LF (0x0a). > > Can anyone explain why this is and, more to the point, tell me how to > > From the documentation: > > | 6.2. Enter versus Return > | > | Prior to version 2.2, Mutt used a default ncurses mode (“nl()”). This > | mode maps keyboard input of either <Enter> or <Return> to the same > | value, which Mutt interpreted as <Return> internally. > | > | However, starting in version 2.2, this mode is turned off, allowing > | <Return> and <Enter> to be mapped separately, if desired. The default > | keyboard mappings set both, but you can override this or create new > | bindings with one or the other (or both). > | > | Note that in terminal application, such as Mutt, <Enter> is the same as > | “\n” and ^J; while <Return> is the same as “\r” and ^M. > Ah, that explains it perfectly, thank you!
> > fix it? > > > bind compose \r send-message # rather than 'y' > ... and that fixes it, more thank you. :-) -- Chris Green
