Re: unbind (all) key bindings
> Whatever you choose to do, once you get used to it, it's the best email > client out there ... Of the various mail user agents I have investigated, only mutt and gnus offer good efficiency in the handling of a large volume of messages. Not coincidentally, neither mutt nor gnus makes use of the rodent. gnus possibly is more efficient than is mutt, but the configuration and the command structure of gnus is rather obscure. More importantly, if Lars Magne Ingebrigtsen -- the creator of gnus, and perhaps the only man who fully understands the package -- falls off the edge of the earth, the popularity of gnus may decline rapidly. In contrast, mutt enjoys considerable popularity and long has been installed by default by Debian. And popularity perhaps is the best guarantee against obsolescence. Thus it is that mutt appears to be the better option in the long term. RLH
Re: core dumps and can't build
* On 26 Nov 2013, Charles E Campbell wrote: > > The core dumps don't do me much good; the mutt I'm using came via a yum > install, so it uses hex addressing. ~/.mutt/cache exists, but no headers, Which yum repo is it from? > I tried building mutt myself (mutt 1.5.21); it builds, but "blesses" me > with: > > Error in /home/cec/.muttrc, line 1: smtp_pass: unknown variable > Error in /home/cec/.muttrc, line 2: smtp_url: unknown variable > source: errors in /home/cec/.muttrc > sh: /usr/local/bin/mutt_dotlock: No such file or directoryError in > /home/cec/.muttrc, line 1: smtp_pass: unknown variable > Error in /home/cec/.muttrc, line 2: smtp_url: unknown variable > source: errors in /home/cec/.muttrc > sh: /usr/local/bin/mutt_dotlock: No such file or directory > Couldn't lock /home/cec/sent You will certainly need the --enable-smtp option to ./configure for this muttrc. If there's an SRPM available for the yum repo you installed from, you might try just using its spec file, but adding --enable-debug. -- David Champion • d...@bikeshed.us
core dumps and can't build
Hello! I've been trying to use mutt from my home computer (it works ok from my work computer). Both use Scientific Linux 6.3. All I get on my home computer is core dumps. Here's my test: echo "TESTING" | mutt -s '[testing] 1-2-3' drchip-@-campbell-family-biz (in the email: remove first three -s, change last one to a period). along with a .muttrc: set smtp_pass="ELIDED" set smtp_url="smtp://smtp.campbellfamily.biz:587" set from="drchip-@-campbell-family-biz" set realname="C Campbell" set editor="gvim" set header_cache=~/.mutt/cache/headers set message_cachedir=~/.mutt/cache/bodies set certificate_file=~/.mutt/certificates set smart_wrap=yes set sort='threads' set sort_aux='last-date-received' The core dumps don't do me much good; the mutt I'm using came via a yum install, so it uses hex addressing. ~/.mutt/cache exists, but no headers, bodies, or certificates. I tried commenting out sort, header_cache, message_cachedir, and certificate_file but that doesn't stop the core dumping. I tried building mutt myself (mutt 1.5.21); it builds, but "blesses" me with: Error in /home/cec/.muttrc, line 1: smtp_pass: unknown variable Error in /home/cec/.muttrc, line 2: smtp_url: unknown variable source: errors in /home/cec/.muttrc sh: /usr/local/bin/mutt_dotlock: No such file or directoryError in /home/cec/.muttrc, line 1: smtp_pass: unknown variable Error in /home/cec/.muttrc, line 2: smtp_url: unknown variable source: errors in /home/cec/.muttrc sh: /usr/local/bin/mutt_dotlock: No such file or directory Couldn't lock /home/cec/sent Could not send the message. I'd appreciate some help! Thank you, Chip Campbell Couldn't lock /home/cec/sent Could not send the message.
Re: unbind (all) key bindings
I understand your concerns about this but I don't think you'll find it a
problem in the long run. I occasionally hit the wrong key and there is always
a way of undoing what I've done (aside from saying 'no' when Mutt actually asks
me if I really want to do something, which personally I like). Shift-W let's
me unclear a flag I've accidentally set and ctrl-c ('do you want to exit
mutt?') gets me out of any other situation (just remember to type n(o) when it
asks). There will be other more sophisticated ways of getting out of certain
situations, but for me these two work and are enough. As to all the other
key-bound functions, it doesn't matter that you don't use them. It's a big
tool box and over the time I've used Mutt I've learned to use some of the tools
when I've felt the need to do something (limit patterns for example). I think
you might be throwing the baby out with the bathwater if you disable all the
keybindings as then you may need to work out how to reinstate some function or
other when you feel the need to use it.
I'd say stick with Mutt as it is, I did, and in a few weeks time I think you'll
find that the keybinding thing is a non-issue. Just my thoughts. Whatever you
choose to do, once you get used to it, it's the best email client out there
IMHO (apart from when I get those pesky complex html messages and have to use
the Gmail web interface!).
On Wed, Nov 27, 2013 at 01:49:04AM +1300, Chris Bannister wrote:
> On Tue, Nov 26, 2013 at 10:09:37AM +0100, Martin Vegter wrote:
> >
> > I have found the following in the manual:
> >
> > bindindex j noop
> > bindindex k noop
> >
> > the problem with this approach is, that I have to unbind every
> > single key-binding explicitly.
>
> It makes no sense to unbind them all, so in reality it is not a
> problem.
>
> > I was wondering whether there is a better solution
>
> I'm wondering how you are actually going to use mutt at all.
> Is the problem you are trying to solve a real one? Have you been bitten
> by it yourself?
>
> You could set the quadoption to ask-yes or ask-no (depending on the
> action) so that a clumsy key press will bring up the dreaded "Are you
> sure you really want to do what you have just asked me to do?" dialog.
>
> --
> "If you're not careful, the newspapers will have you hating the people
> who are being oppressed, and loving the people who are doing the
> oppressing." --- Malcolm X
--
Dr Martin Orwin
Senior Lecturer in Somali and Amharic
Associate Head of the Department of the Languages and Cultures of Africa
SOAS
Re: unbind (all) key bindings
On Tue, Nov 26, 2013 at 10:09:37AM +0100, Martin Vegter wrote: > > I have found the following in the manual: > > bindindex j noop > bindindex k noop > > the problem with this approach is, that I have to unbind every > single key-binding explicitly. It makes no sense to unbind them all, so in reality it is not a problem. > I was wondering whether there is a better solution I'm wondering how you are actually going to use mutt at all. Is the problem you are trying to solve a real one? Have you been bitten by it yourself? You could set the quadoption to ask-yes or ask-no (depending on the action) so that a clumsy key press will bring up the dreaded "Are you sure you really want to do what you have just asked me to do?" dialog. -- "If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing." --- Malcolm X
Re: unbind (all) key bindings
On 2013-11-26 00:05, Patrick Shanahan wrote: * Martin Vegter [11-25-13 17:33]: as a new user, I feel intimidated by the many key bindings in Mutt. Not only do I see no chance of ever needing more than 5% of them, but I am afraid that by accidentally pressing some key, I will perform some "action" without knowing what happened. I have very simple requirements from my email client. I don't need two separate key binding for "next-entry" and "next-undeleted", for example. I would like to unbind all key bindings, so that I can explicitly define only those, that I am actually going to use. While googling, I have discovered that I am not the only one having this problem. There even seems to be a patch called "unbind": http://home.uchicago.edu/~dgc/mutt/#unbind but only for version 1.4 and 1.5.1. I am using mutt version 1.5.21-6.2+deb7u1, so I am not sure if that would work. Could somebody please advise, what would be the best way to do it? I would look at the help file in mutt and add to ~/.muttrc bind /dev/null and then you would have a record of what you have changed and have a simple way to revert. not tested. I have found the following in the manual: bindindex j noop bindindex k noop the problem with this approach is, that I have to unbind every single key-binding explicitly. I was wondering whether there is a better solution
