<<< Date Index >>>     <<< Thread Index >>>

Re: [Mutt] #3153: "recall" setting lags "postponed" setting



#3153: "recall" setting lags "postponed" setting
-----------------------+----------------------------------------------------
  Reporter:  agriffis  |       Owner:  brendan 
      Type:  defect    |      Status:  accepted
  Priority:  minor     |   Milestone:  1.6     
 Component:  mutt      |     Version:  1.5.19  
Resolution:            |    Keywords:          
-----------------------+----------------------------------------------------
Changes (by brendan):

  * owner:  mutt-dev => brendan
  * status:  new => accepted


Old description:

> server1/INBOX.postponed contains a message
> server2/INBOX.postponed does not
>
> set postponed=imaps://server1/INBOX.postponed
> set recall=ask-no
>
> compose, mutt asks if you'd like to recall, just cancel with ctrl-g
>
> set postponed=imaps://server2/INBOX.postponed
>
> compose, mutt asks if you'd like to recall, even though there's nothing
> in imaps://server2/INBOX.postponed.  It's remembering from the old
> postponed box.  If you hit 'y' then it reports there's nothing there, and
> subsequently it won't ask.
>
> set postponed=imaps://server1/INBOX.postponed
>
> compose, mutt doesn't ask because it's remembering from
> imaps://server2/INBOX.postponed.  However after <recall-message> is
> explicitly called, then mutt will correctly ask again.

New description:

 `server1/INBOX.postponed` contains a message
 `server2/INBOX.postponed` does not
 {{{
 set postponed=imaps://server1/INBOX.postponed
 set recall=ask-no
 }}}
 compose, mutt asks if you'd like to recall, just cancel with `^g`
 {{{
 set postponed=imaps://server2/INBOX.postponed
 }}}
 compose, mutt asks if you'd like to recall, even though there's nothing in
 `imaps://server2/INBOX.postponed`.  It's remembering from the old
 postponed box.  If you hit `y` then it reports there's nothing there, and
 subsequently it won't ask.
 {{{
 set postponed=imaps://server1/INBOX.postponed
 }}}
 compose, mutt doesn't ask because it's remembering from
 `imaps://server2/INBOX.postponed`.  However after `<recall-message>` is
 explicitly called, then mutt will correctly ask again.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3153#comment:2>
Mutt <http://www.mutt.org/>
The Mutt mail user agent