On 13Aug2018 21:06, TJ Hayes <[email protected]> wrote:
@Cameron Simpson
Thank you for your help. Here is what I get when I try the suggestions given:
Try commenting this line out of your config and retry. I don't have this
explicitly in my settings, it comes from mutt's defaults for me.
Commenting out "bind <return> display-message" from my muttrc has no impact.
The <return> key still does nothing when I press it in index mode.
Ok. Try grepping for "bind" in all your mutt settings files.
Also try running "mutt -F /dev/null" to bypass all the configuration.
This worked!! When I run mutt with no config file (muttrc), the <Return> key
does function properly to display-message in index mode. This is a clue that my
muttrc is giving me the trouble.
Yes. Maybe there's a stray bind somewhere. Try a grep i.e. get the computer to
look instead of looking by eye. My own eye likes to see what should be there
instead of what is actually there.
Also, I think -F skips the system muttrc as well.
Try moving your muttrc sideways:
mv ~/.muttrc ~/DOTmuttrc
and test mutt again. If it is still bad then we start suspecting the system
muttrc stuff.
Also, I verified that typing ? to show keybinds DOES show that display-message and
"display a message" are listed for <Return>.
Urgh.
Your keypress test argues against this next idea, but does your muttrc invoke
anything that may muck with the keyboard, like the "stty" command?
> Do you have another version of mutt to hand to run against the
same setup for comparison?
I do not have another version to run with the same setup.
** One new bit of information: this behavior started after I upgraded my system from
Ubuntu-Budgie 17.10 to Ubuntu-Budgie 18.04. I was second guessing myself about this,
wondering if I only thought that <Return> used to open an email message.
What you want is mutt's default behaviour, so your beliefs sound right to me.
However, I am 95% sure that mutt worked fine before the upgrade to my Linux
OS. I wonder if the newer version of Ubuntu, or the upgrade process itself
somehow messed up the inner workings of my mutt. Searching the Ubuntu help
pages gave no hints that anyone else has run into this.
Ok, look for bind commands in the system muttrc. My local Ubuntu is well
behind, and I mostly live on a Mac anyway. However on Ubuntu the system muttrc
is in the file /etc/Muttrc and the files /etc/Muttrc.d/*.rc.
Mine has:
[//etc]borg*> grep bind /etc/Muttrc /etc/Muttrc.d/*
/etc/Muttrc:# emacs-like bindings
/etc/Muttrc:bind editor "\e<delete>" kill-word
/etc/Muttrc:bind editor "\e<backspace>" kill-word
/etc/Muttrc:bind editor <delete> delete-char
/etc/Muttrc:#bind pager <up> previous-line
/etc/Muttrc:#bind pager <down> next-line
/etc/Muttrc:bind browser y exit
Maybe you've got something exciting and new.
My next steps:
(1) Mess with my muttrc to find out what is causing this strange behavior.
(2) Try another version of mutt. Maybe I can figure out how to compile the
newest version of mutt 1.10.0.
Fetch source from mutt.org. Unpack source. In the source tree:
./configure --prefix=/opt/mutt-1.10.0 && make && echo OK
Then "mkdir /opt/mutt-1.10.0" and "make install && echo OK".
You may want a billion special switches for configure, depending what you make
use of. Last time I did this I went:
LDFLAGS=-L/opt/local/lib CFLAGS=-I/opt/local/include ./configure
--prefix=/opt/mutt-1.10.0--`daycode` --with-ssl --with-idn --enable-gpgme
--enable-sidebar --enable-compressed --enable-pop --enable-imap --enable-smtp
--enable-exact-address --enable-hcache && echo YES
The envvars are to suck in the MacPorts libraries. You won't need that but you
might need a bunch of "*-dev" apt packages.
Cheers,
Cameron Simpson <[email protected]>
