Re: Press any key to continue

2023-09-08 Thread Ed Blackman
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

Re: Press any key to continue

2015-09-25 Thread Christian Ebert
* 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

Re: Press any key to continue

2015-09-21 Thread Jon LaBadie
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

Re: Press any key to continue

2015-09-21 Thread Cameron Simpson
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

Re: Press any key to continue

2015-09-21 Thread David Champion
* 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

Re: Press any key to continue

2015-09-21 Thread Cameron Simpson
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

Re: Press any key to continue

2015-09-21 Thread Patrick Shanahan
* 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

Re: Press any key to continue

2015-09-21 Thread Christian Ebert
* 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?

Re: Press any key to continue

2015-09-21 Thread David Champion
* 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,

Re: Press any key to continue

2015-09-21 Thread Ben Boeckel
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

Re: Press any key to continue

2015-09-21 Thread Ben Boeckel
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 =

Re: Press any key to continue

2015-09-21 Thread Patrick Shanahan
* 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

Re: Press any key to continue

2015-09-21 Thread David Champion
* 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

Re: Press any key to continue

2015-09-21 Thread Patrick Shanahan
* 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,

Re: Press any key to continue

2015-09-21 Thread Jon LaBadie
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

Press any key to continue

2015-09-20 Thread Ian Zimmerman
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 may save their output in a file, so their

Re: Press any key to continue

2015-09-20 Thread Cameron Simpson
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

Re: pipe-message without the press any key to continue

2008-02-29 Thread Colby W.
On Fri, Feb 29, 2008 at 7:53 AM, Nathan Huesken [EMAIL PROTECTED] wrote: Hi, I have a macro, which pipes a message to a script: macro index,pager p 'pipe-message~/.mutt/scriptenterfuther-stuf' So far so good, what I don't like is the Press any key to continue... and the fact, that I

pipe-message without the press any key to continue

2008-02-29 Thread Nathan Huesken
Hi, I have a macro, which pipes a message to a script: macro index,pager p 'pipe-message~/.mutt/scriptenterfuther-stuf' So far so good, what I don't like is the Press any key to continue... and the fact, that I need to press a key to continue. Can this somehow be avoided? Thanks! nathan

Re: Press any key to continue ...

2001-02-21 Thread Michael Tatge
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 muttrc

Re: Press any key to continue ...

2001-02-21 Thread Zach Thompson
) recently after an update mutt even asks me to press when I start it up. So how do I remove this behaviour, So that I never see this phrase "Press any key to continue..." again. Searched the docs, but didn't find anything, somebody an idea??? Thankx -- Jeroen Valcke

Press any key to continue ...

2001-02-21 Thread Jeroen Valcke
Press any key to continue..." again. Searched the docs, but didn't find anything, somebody an idea??? Thankx -- Jeroen Valcke [EMAIL PROTECTED] ICQ# 30116911 Home page: http://www.valcke.com/jeroen Phone +32(0)56 32 91 37 Mobile +32(0)486 88 2