Your message dated Sun, 26 Feb 2006 18:55:30 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#354422: mutt-ng: do not check for new mail while in compose
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: mutt-ng
Version: 0.0+20060213-1
Severity: wishlist
Tags: patch

I've got quite a few of imap mailboxes which mutt is dedicated to
monitor, but it started to annoy me too much now when it "slept" for
up to 10 seconds whenever I leave vim while composing an email.
That is why I decided that it will be useful to have that "forced"
check for new mail optional. Please see patch below which provides an
option sidebar_mail_check_compose (yes by default to confirm previous
behavior)

--- muttng.orig/mutt-ng-0.0+20060213/compose.c  2006-02-11 17:09:29.000000000 
-0500
+++ mutt-ng-0.0+20060213/compose.c      2006-02-25 22:40:34.000000000 -0500
@@ -563,8 +563,11 @@
     menu->help =
       mutt_compile_help (helpstr, sizeof (helpstr), MENU_COMPOSE,
                          ComposeHelp);
-
-  if (option (OPTMBOXPANE))
+  /* [EMAIL PROTECTED]: 
+   * I don't want that delay to be whenever I edit the mail: 
+   * OPTSIDEBARMAILCHECKCOMPOSE is for that purpose
+   */
+  if (option (OPTMBOXPANE) && option (OPTSIDEBARMAILCHECKCOMPOSE))
     buffy_check (1);
   while (loop) {
 #ifdef USE_NNTP
--- muttng.orig/mutt-ng-0.0+20060213/init.h     2006-01-13 03:51:23.000000000 
-0500
+++ mutt-ng-0.0+20060213/init.h 2006-02-25 22:33:27.000000000 -0500
@@ -1584,6 +1584,11 @@
    ** .pp
    ** The width of the sidebar.
    */
+  {"sidebar_mail_check_compose", DT_BOOL, R_BOTH, OPTSIDEBARMAILCHECKCOMPOSE, 
"yes" },
+  /*
+   ** .pp
+   ** If \fIset\fP, checks for new mail when sidebar is displaied in compose 
mode.
+   */
   {"sidebar_newmail_only", DT_BOOL, R_BOTH, OPTSIDEBARNEWMAILONLY, "no" },
   /*
    ** .pp
--- muttng.orig/mutt-ng-0.0+20060213/mutt.h     2005-10-22 20:52:43.000000000 
-0400
+++ mutt-ng-0.0+20060213/mutt.h 2006-02-25 23:19:57.000000000 -0500
@@ -519,6 +519,7 @@
 #endif
   OPTSHORTENHIERARCHY,          /* set when to shorten "hierarchies" in the 
sidebar */
   OPTSIDEBARNEWMAILONLY,
+  OPTSIDEBARMAILCHECKCOMPOSE,   /* set when to check for new mail while in 
compose mode */
   OPTMAX
 };
 



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

Versions of packages mutt-ng depends on:
ii  exim4                         4.60-3     metapackage to ease exim MTA (v4) 
ii  exim4-daemon-light [mail-tran 4.60-3     lightweight exim MTA (v4) daemon
ii  libc6                         2.3.5-12   GNU C Library: Shared libraries an
ii  libgnutls11                   1.0.16-14  GNU TLS library - runtime library
ii  libgpg-error0                 1.1-4      library for common error values an
ii  libgpgme11                    1.1.0-1    GPGME - GnuPG Made Easy
ii  libidn11                      0.5.18-1   GNU libidn library, implementation
ii  libncursesw5                  5.5-1      Shared libraries for terminal hand
ii  libqdbm11                     1.8.33-2   QDBM Database Libraries [runtime]
ii  libsasl2                      2.1.19-1.9 Authentication abstraction library

mutt-ng recommends no packages.

-- no debconf information


--Yarik


--- End Message ---
--- Begin Message ---
On Sun, 26 Feb 2006 the mental interface of
Yaroslav Halchenko told:

> Hi Rocco,
> 
> Yeap - it was me :-)
> 
> Ok - I will give a try to not forcing check with 0, which indeed sounds
> more logical and 'uniform' way to handle this situation.
> ...
> ok - I gave it a try -- and it works nice (why the heck I've decided to
> "Fix" things in the middle of the night? :-)).

Debian bug closed ;)

Elimar

-- 
    .~.
    /V\   L   I   N   U   X
   /( )\ >Phear the Penguin<
   ^^-^^

--- End Message ---

Reply via email to