I know this is a blast from the past, but I wanted to thank Christian for this
long-ago message! I often put aside messages for when I have time to explore
something that is interesting to me. I am not so good at actually going back
and looking at them later.I had a little time recently an
* Ben Boeckel on Monday, September 21, 2015 at 14:36:34 -0400
> On Mon, Sep 21, 2015 at 12:32:02 -0500, David Champion wrote:
>> set my_wait_key=$wait_key
>> unset wait_key
>> set wait_key=$my_wait_key
>
> Well, that looks nasty, but it works:
>
>macro generic \Cy \
>":set my_wait_key
On 21Sep2015 23:48, Jon LaBadie wrote:
On Tue, Sep 22, 2015 at 11:03:18AM +1000, Cameron Simpson wrote:
On 21Sep2015 14:36, Ben Boeckel wrote:
>On Mon, Sep 21, 2015 at 12:32:02 -0500, David Champion wrote:
>>set my_wait_key=$wait_key
>>unset wait_key
>>set wait_key=$my_wait_key
>
>Well, that l
On Tue, Sep 22, 2015 at 11:03:18AM +1000, Cameron Simpson wrote:
> On 21Sep2015 14:36, Ben Boeckel wrote:
> >On Mon, Sep 21, 2015 at 12:32:02 -0500, David Champion wrote:
> >>set my_wait_key=$wait_key
> >>unset wait_key
> >>set wait_key=$my_wait_key
> >
> >Well, that looks nasty, but it works:
> >
* On 21 Sep 2015, Cameron Simpson wrote:
>
> So you might have ",y" mapped to a macro to save various settings (i.e. save
> everything that any of your macros fiddle with) and ",Y" mapped to pull the
> values back from $my_foo et al into the settings again.
>
> Then put ",y" at the start of your
On 21Sep2015 14:36, Ben Boeckel wrote:
On Mon, Sep 21, 2015 at 12:32:02 -0500, David Champion wrote:
set my_wait_key=$wait_key
unset wait_key
set wait_key=$my_wait_key
Well, that looks nasty, but it works:
macro generic \Cy \
":set my_wait_key = $wait_key:unset wait_keykillall -USR
* Jon LaBadie [09-21-15 17:27]:
> On Mon, Sep 21, 2015 at 02:36:34PM -0400, Ben Boeckel wrote:
> > On Mon, Sep 21, 2015 at 12:32:02 -0500, David Champion wrote:
> > > set my_wait_key=$wait_key
> > > unset wait_key
> > > set wait_key=$my_wait_key
> >
> > Well, that looks nasty, but it works:
> >
* On 21 Sep 2015, Jon LaBadie wrote:
> >
> > I still think some command or function to do this would help a lot.
> > Wrapping all functions like this is…tedious to say the least. It also
> > makes reading these things annoying since the meat of the binding is
> > buried 65 characters into the lin
On Mon, Sep 21, 2015 at 02:36:34PM -0400, Ben Boeckel wrote:
> On Mon, Sep 21, 2015 at 12:32:02 -0500, David Champion wrote:
> > set my_wait_key=$wait_key
> > unset wait_key
> > set wait_key=$my_wait_key
>
> Well, that looks nasty, but it works:
>
> macro generic \Cy \
> ":set my_wait
* Ben Boeckel [09-21-15 13:34]:
> On Mon, Sep 21, 2015 at 11:38:23 -0400, Patrick Shanahan wrote:
> > No, you don't chang mutt to accommodate vim as many, maybe most, use
> > another editor. Mutt has a manner available to provide the state you
> > wish, use it. And, as with many programs, you ma
On Mon, Sep 21, 2015 at 12:32:02 -0500, David Champion wrote:
> set my_wait_key=$wait_key
> unset wait_key
> set wait_key=$my_wait_key
Well, that looks nasty, but it works:
macro generic \Cy \
":set my_wait_key = $wait_key:unset
wait_keykillall -USR1 offlineimap:set wait_key =
$my_w
* On 21 Sep 2015, Ben Boeckel wrote:
> On Mon, Sep 21, 2015 at 11:38:23 -0400, Patrick Shanahan wrote:
> > No, you don't chang mutt to accommodate vim as many, maybe most, use
> > another editor. Mutt has a manner available to provide the state you
> > wish, use it. And, as with many programs, y
On Mon, Sep 21, 2015 at 11:38:23 -0400, Patrick Shanahan wrote:
> No, you don't chang mutt to accommodate vim as many, maybe most, use
> another editor. Mutt has a manner available to provide the state you
> wish, use it. And, as with many programs, you may have to keep track of
> the conditions
* Ben Boeckel [09-21-15 11:18]:
> On Mon, Sep 21, 2015 at 14:41:08 +1000, Cameron Simpson wrote:
> > I have:
> >
> > set wait_key=no
> >
> > In principle you can write macros to turn this on (or off) around specific
> > actions.
>
> Vim has the "silent" command. Maybe Mutt could have a simil
On Mon, Sep 21, 2015 at 14:41:08 +1000, Cameron Simpson wrote:
> I have:
>
> set wait_key=no
>
> In principle you can write macros to turn this on (or off) around specific
> actions.
Vim has the "silent" command. Maybe Mutt could have a similar one for
such command executions. Having to write
* Ian Zimmerman on Sunday, September 20, 2015 at 21:36:24 -0700
> Mutt asks me this after any pipe-message command. I can see how it is
> necessary for commands that produce output; otherwise I wouldn't get a
> chance to see the output. But what about commands that produce nothing
> on stdout? S
On 20Sep2015 21:36, Ian Zimmerman wrote:
Mutt asks me this after any pipe-message command. I can see how it is
necessary for commands that produce output; otherwise I wouldn't get a
chance to see the output. But what about commands that produce nothing
on stdout? Some non-interactive commands
Set this in your .muttrc so mutt won't prompt for a key after executing
something in a shell:
set wait_key=no
Zach
Jeroen Valcke said:
> Hello all,
>
> Mutt has this habit of always asking me to press a key to continue, for
> example when I want to view an attachment or an url (with urlview)
>
Jeroen Valcke muttered:
> Mutt has this habit of always asking me to press a key to continue, for
> recently after an update mutt even asks me to press when I start it up.
> So how do I remove this behaviour,
Most likely you updated from a rather old version. There were some
changes to the muttr
19 matches
Mail list logo
