On Saturday, 15 November 2008 at 16:02, Gary Johnson wrote: > In the thread, "Segmentation fault from mutt-1.5.17 with SMTP," I > wrote that when using mutt's built-in SMTP client to send messages > in batch mode, mutt printed the following messages: > > Looking up mailsvr.spk.agilent.com... > Connecting to mailsvr.spk.agilent.com... > Sending message... 0K/0.4K (0%) > Sending message... 0K/0.4K (0%) > Sending message... 0K/0.4K (0%) > Sending message... 0K/0.4K (0%) > Sending message... 0K/0.4K (0%) > Sending message... 0K/0.4K (0%) > Sending message... 0K/0.4K (0%) > Sending message... 0K/0.4K (0%) > Sending message... 0K/0.4K (0%) > Sending message... 0K/0.4K (0%) > Sending message... 0K/0.4K (0%) > Sending message... 0K/0.4K (0%) > Sending message... 0K/0.4K (0%) > Sending message... 0K/0.4K (0%) > > Messages like those are normally printed only in interactive mode. > I think it was just an oversight that they are printed in batch mode > as well. The attached patch fixes that behavior. > > The changes were made to source files from the HEAD branch of the > mercurial repository at http://dev.mutt.org/hg/mutt, updated last > night. Thanks! I've applied your changes (with a minor modification to check OPTNOCURSES in mutt_progress_* instead of at the caller).
Attachment:
pgpVtYodP7W2l.pgp
Description: PGP signature