Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 36B64431FBC for ; Tue, 10 Sep 2013 07:12:59 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EEOfFkDjcaJe for ; Tue, 10 Sep 2013 07:12:54 -0700 (PDT) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 81B38431FAE for ; Tue, 10 Sep 2013 07:12:54 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1VJOgV-0008JF-Mw; Tue, 10 Sep 2013 11:12:51 -0300 Received: (nullmailer pid 19514 invoked by uid 1000); Tue, 10 Sep 2013 14:12:47 -0000 From: David Bremner To: Mark Walters , notmuch@notmuchmail.org Subject: Re: [PATCH] emacs: show: stop stderr appearing in buffer In-Reply-To: <1378502198-7980-1-git-send-email-markwalters1009@gmail.com> References: <1378502198-7980-1-git-send-email-markwalters1009@gmail.com> User-Agent: Notmuch/0.16+71~gfd656d7 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Tue, 10 Sep 2013 11:12:47 -0300 Message-ID: <87r4cwojds.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Sep 2013 14:12:59 -0000 > Ideally, we would put this output in the notmuch errors buffer but the > handler is called asynchronously so we don't know when the output will > appear. Thus if we put it straight into the errors buffer it could get > interleaved with other errors, otoh we can't easily tell when we > have got all the error output so can't wait until the process is complete. Hi Mark; I think your patch is OK, but would it be much harder to created a named buffer like *notmuch-view-$message-d* ? (using e.g. the code from notmuch-show). I might make debugging easier. Of course those buffers would accumulate, along with show, search and pick buffers... Or we could push this as is, and add some debugging facility later like a variable notmuch-view-errors-buffer. d