Re: unbind (all) key bindings

2013-11-27 Thread David Champion
* On 25 Nov 2013, Martin Vegter wrote: 
> 
> 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.

Hi Martin -

I think the other responses on this thread are appropriate, and you
should consider whether you really want to unbind everything.  That
said, as the author of the unbind patch that you cited: no, it won't
work with a current mutt.  It's very out of date.  I took some time to
update and improve the patch and you'll find the result here:

http://permalink.gmane.org/gmane.mail.mutt.devel/21157

(For anyone familiar with the unbind saga and its intricacies, this
patch finally does a real unbind, not a bind to noop.)

-- 
David Champion • d...@bikeshed.us


Re: unbind (all) key bindings

2013-11-27 Thread Martin Orwin
On Thu, Nov 28, 2013 at 01:31:14AM +1300, Chris Bannister wrote:
> On Tue, Nov 26, 2013 at 01:41:55PM +, Martin Orwin wrote:
> > 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!).
> 
> I notice you are using mutt as the MUA. How did you manage to screw up
> this post so badly?

I see my error.  Apologies.  I'm not sure how that happened.


Re: unbind (all) key bindings

2013-11-27 Thread Chris Bannister
On Tue, Nov 26, 2013 at 01:41:55PM +, Martin Orwin wrote:
> 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!).

I notice you are using mutt as the MUA. How did you manage to screw up
this post so badly?

-- 
"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

2013-11-26 Thread rlharris
> 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: unbind (all) key bindings

2013-11-26 Thread Martin Orwin
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

2013-11-26 Thread Chris Bannister
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

2013-11-26 Thread Martin Vegter

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


Re: unbind (all) key bindings

2013-11-25 Thread Patrick Shanahan
* 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.
-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2
Registered Linux User #207535@ http://linuxcounter.net


unbind (all) key bindings

2013-11-25 Thread Martin Vegter

hello,

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?


Re: Unbind All?

2001-02-22 Thread Jay Rossiter / Signe

On 02/22, David Champion rearranged the electrons to read:
> On 2001.02.22, in <[EMAIL PROTECTED]>,
>   "Jay Rossiter / Signe" <[EMAIL PROTECTED]> wrote:
>  >
>  > Is there a way to unbind all keys with one, or a small series, of
>  > commands?  I'm trying to set mutt up so that the only commands bound are
>  > ones that I explicitly set.  I'm tired of tpyoing a key and ending up in
>  > some menu or option that I didn't want.
>  >
>  > Hopefully, I can find something short of "Unbind each key seperately",
>  > but if anyone has a script to do this, that'd work, too.  :p
> 
> There's not now, but I have a patch to define that permits "unbind" and
> "unmacro" to do this.
> 
> See
>   http://home.uchicago.edu/~dgc/mutt/#unbind
> 
> That patch was for mutt 1.3.2, but might apply on 1.2.5.  If you have
> trouble, let me know and I'll backport it.

The patch worked beautifully on 1.2.5.  I'd suggest getting this
patch officially added to the source, or at least put on the contrib
page. The users of this may be few and far between, but they'll
appreaciate it greatly.  (As I do.)

Thanks.

-- 
PGP Key available on Keyservers  -  UIN: 1878946
ID:  0x81279EE9  -  WebPage:  http://www.speakeasy.org/~signe
Fingerprint:  CB63 1EB8 8150 A01A F017  C79B 1DC5 3BFF 8127 9EE9




Re: Unbind All?

2001-02-22 Thread David Champion

On 2001.02.22, in <[EMAIL PROTECTED]>,
"Jay Rossiter / Signe" <[EMAIL PROTECTED]> wrote:
> 
> Is there a way to unbind all keys with one, or a small series, of
> commands?  I'm trying to set mutt up so that the only commands bound are
> ones that I explicitly set.  I'm tired of tpyoing a key and ending up in
> some menu or option that I didn't want.
>
> Hopefully, I can find something short of "Unbind each key seperately",
> but if anyone has a script to do this, that'd work, too.  :p

There's not now, but I have a patch to define that permits "unbind" and
"unmacro" to do this.

See
http://home.uchicago.edu/~dgc/mutt/#unbind

That patch was for mutt 1.3.2, but might apply on 1.2.5.  If you have
trouble, let me know and I'll backport it.

-- 
 -D.[EMAIL PROTECTED]NSITUniversity of Chicago



Unbind All?

2001-02-22 Thread Jay Rossiter / Signe


I know this is probably a longshot (I looked through the archives
already and found nothing.)

Is there a way to unbind all keys with one, or a small series, of
commands?  I'm trying to set mutt up so that the only commands bound are
ones that I explicitly set.  I'm tired of tpyoing a key and ending up in
some menu or option that I didn't want.

Hopefully, I can find something short of "Unbind each key seperately",
but if anyone has a script to do this, that'd work, too.  :p

-- 
PGP Key available on Keyservers  -  UIN: 1878946
ID:  0x81279EE9  -  WebPage:  http://www.speakeasy.org/~signe
Fingerprint:  CB63 1EB8 8150 A01A F017  C79B 1DC5 3BFF 8127 9EE9