Re: [SOLVED] "set include=yes" bypasses Compose Menu

2013-04-16 Thread James Griffin
Mon 15.Apr'13 at 10:18:43 -0700 Kevin J. McCarthy > rj wrote: > > On Mon 15 at 12:04 AM -0400, rj wrote: > > > > > That would mean that although this line cures the problem, something else > > > is causing it. > > > > What was causing it was this key binding: > >

Re: [off-topic] Re: [not-quite-SOLVED] "set include=yes" bypasses Compose Menu

2013-04-15 Thread rj
On Mon 15 at 12:19 PM -0600, "s. keeling" wrote: > . . . Why do you need to explicitly set editor=vim? Or, are you just > doing that to get the "+10" functionality? That's correct. Though I set up that macro quite awhile ago I think if I could have made it more elegant, i.e., with fewer comm

[off-topic] Re: [SOLVED] "set include=yes" bypasses Compose Menu

2013-04-15 Thread s. keeling
Incoming from Kevin J. McCarthy: > rj wrote: > > > > macro index,pager r ":set editor='vim +10'^M{^M" "reply with quoting" > > Great news that you figured it out! I'm happy for you (him/her?) too. I've suffered through a few episodes like that of my own ("Why's this happening?!?"). However

Re: [SOLVED] "set include=yes" bypasses Compose Menu

2013-04-15 Thread Kevin J. McCarthy
rj wrote: > On Mon 15 at 12:04 AM -0400, rj wrote: > > > That would mean that although this line cures the problem, something else > > is causing it. > > What was causing it was this key binding: > bind index,pager { reply# Restored to 'r' in macro below. > > combined with this macro:

Re: [SOLVED] "set include=yes" bypasses Compose Menu

2013-04-14 Thread Nikola Petrov
I suspect that your fat fingers played there ;) Glad you sorted it out. -- Nikola On Mon, Apr 15, 2013 at 12:49:02AM -0400, rj wrote: > On Mon 15 at 12:04 AM -0400, rj wrote: > > > That would mean that although this line cures the problem, something else > > is causing it. > > What was causin

Re: [SOLVED] "set include=yes" bypasses Compose Menu

2013-04-14 Thread rj
On Mon 15 at 12:04 AM -0400, rj wrote: > That would mean that although this line cures the problem, something else > is causing it. What was causing it was this key binding: bind index,pager { reply# Restored to 'r' in macro below. combined with this macro: macro index,pager r ":set

Re: "set include=yes" bypasses Compose Menu

2013-04-14 Thread Russell Hoover
On Sun 14 at 08:06 PM -0700, "Kevin J. McCarthy" wrote: > I'm not super familiar with the details of send-hook but I suspect > multiple commands may not be allowed. Try breaking the last line into > two parts and see if that helps: I think I wasn't quite clear: I do *not* have the problem whe

Re: "set include=yes" bypasses Compose Menu

2013-04-14 Thread Kevin J. McCarthy
rj wrote: > On Sat 13 at 07:28 PM -0700, "Kevin J. McCarthy" wrote: > > My guess would be a send-hook or reply-hook is causing this. > > send-hook.'unmy_hdr From:' > send-hook '~Chfha-members' 'my_hdr From: rj ' > # send-hook '(~Czsh-users| ~Cmutt-users| ~Cvex)' 'set crypt_autosig

Re: "set include=yes" bypasses Compose Menu

2013-04-14 Thread rj
On Sat 13 at 07:28 PM -0700, "Kevin J. McCarthy" wrote: > My guess would be a send-hook or reply-hook is causing this. Thanks for the response. Your suggestion helped me identify the problem, which was this combination of send-hooks: send-hook.'unmy_hdr From:' send-hook '~Chfha-

Re: "set include=yes" bypasses Compose Menu

2013-04-13 Thread Kevin J. McCarthy
rj wrote: > I'm finding that if I set > > set include=yes > > when I finish writing a reply in vim, the message gets sent *instantly* > upon my hitting the command to exit the editor. The Compose Menu doesn't > appear at all. > > If I unset include=yes, I no longer have that problem, but

"set include=yes" bypasses Compose Menu

2013-04-13 Thread rj
I'm finding that if I set set include=yes when I finish writing a reply in vim, the message gets sent *instantly* upon my hitting the command to exit the editor. The Compose Menu doesn't appear at all. If I unset include=yes, I no longer have that problem, but then of course I get the