Re: [RFC PATCH 1/1] add --stderr option

diff --git a/24/fb643f4473da27a6af78603b3ff3fc4c55c03e b/24/fb643f4473da27a6af78603b3ff3fc4c55c03e
new file mode 100644 (file)
index 0000000..ecf158c
--- /dev/null
+++ b/24/fb643f4473da27a6af78603b3ff3fc4c55c03e
@@ -0,0 +1,94 @@
+Return-Path: <tomi.ollila@iki.fi>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id C5A4C431FBF\r
+       for <notmuch@notmuchmail.org>; Wed, 22 May 2013 00:51:02 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id xQerEs0mkee5 for <notmuch@notmuchmail.org>;\r
+       Wed, 22 May 2013 00:50:54 -0700 (PDT)\r
+Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])\r
+       by olra.theworths.org (Postfix) with ESMTP id 719E7431FB6\r
+       for <notmuch@notmuchmail.org>; Wed, 22 May 2013 00:50:54 -0700 (PDT)\r
+Received: from guru.guru-group.fi (localhost [IPv6:::1])\r
+       by guru.guru-group.fi (Postfix) with ESMTP id 7B1E41002C3;\r
+       Wed, 22 May 2013 10:50:46 +0300 (EEST)\r
+From: Tomi Ollila <tomi.ollila@iki.fi>\r
+To: Justus Winter <4winter@informatik.uni-hamburg.de>, notmuch@notmuchmail.org\r
+Subject: Re: [RFC PATCH 1/1] add --stderr option\r
+In-Reply-To: <20130521195549.6550.53636@thinkbox.jade-hamburg.de>\r
+References: <1369161750-12342-1-git-send-email-tomi.ollila@iki.fi>\r
+       <20130521195549.6550.53636@thinkbox.jade-hamburg.de>\r
+User-Agent: Notmuch/0.15.2+115~g12cf6af (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-unknown-linux-gnu)\r
+X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL\r
+       $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F\r
+       !)g;OY^,BjTbr)Np:%c_o'jj,Z\r
+Date: Wed, 22 May 2013 10:50:46 +0300\r
+Message-ID: <m261yb4fmx.fsf@guru.guru-group.fi>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 22 May 2013 07:51:02 -0000\r
+\r
+On Tue, May 21 2013, Justus Winter <4winter@informatik.uni-hamburg.de> wrote:\r
+\r
+> Quoting Tomi Ollila (2013-05-21 20:42:30)\r
+>> ---\r
+>> \r
+>> Note quickly written untested code (but compiles!), just to show an idea...\r
+>> \r
+>> This implements (i hope) curl(1) --stderr option in notmuch(1):\r
+>> \r
+>>        --stderr <file>\r
+>>               Redirect  all writes to stderr to the specified file instead. If\r
+>>               the file name is a plain '-', it is instead written to stdout.\r
+>> \r
+>> This would be useful in emacs interface.\r
+>\r
+> Hm, shouldn't it be possible to bind a pipe(2) to stderr instead? I\r
+> mean in the process of running the notmuch binary (i.e. somewhere\r
+> along the lines of fork and exec)?\r
+\r
+Yes, if emacs(1) were smarter ;/\r
+\r
+> I've implemented this for alot, which does not use the binary but\r
+> directly calls into libnotmuch, but does so in a helper process. Said\r
+> helper has a pipe(2) on stderr and the alot process reads from it and\r
+> turns any line into a log message.\r
+\r
+It is unfortunate that you have to do that -- libnotmuch should not\r
+emit anything to stderr... We've briefly discussed what changes\r
+are needed to libnotmuch what could be done there but... :)\r
+\r
+<questionable advice>\r
+Instead of running separate process you could have both ends of the\r
+pipe in same process and check after libnotmuch call whether there \r
+is data in the reading end of the pipe. I think pipe buffers like 4k\r
+of data. If you used socketpair(2) that buffers 100k of data by\r
+default in Linux systems. Still, using nonblocking fds are\r
+advisable if using this hack ;D\r
+</questionable advice>\r
+\r
+>\r
+> Justus\r
+\r
+Tomi\r