From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Carl Worth <cworth@cworth.org>,
Jameson Rollins <jrollins@finestructure.net>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] emacs: send notmuch-query stderr to /dev/null
Date: Thu, 27 Jan 2011 12:29:05 +0100 [thread overview]
Message-ID: <87zkqm7fge.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <87lj27ymqg.fsf@yoom.home.cworth.org>
On Thu, 27 Jan 2011, Carl Worth wrote:
> On Wed, 26 Jan 2011 12:57:50 -0800, Jameson Rollins <jrollins@finestructure.net> wrote:
> > The call-process to notmuch in notmuch-query.el was previously sending
> > stderr into the output buffer. This means that if there is any stderr
> > the JSON parsing breaks. Unfortunately call-process does not support
> > sending stderr to a separate buffer or to the minibuffer [0], but it
> > does support sending it to /dev/null. So we do that here instead.
> >
> > [0] a bug was filed against emacs (#7842)
>
> Thanks! I had wondered what those json errors were about. I've committed
> this.
>
> I am a bit concerned about throwing the error output away, of course,
> (so we'll wait for that fix to emacs---thanks for submitting a bug
> report). Do you have a sense of what kinds of output we are getting on
> stderr?
I do not know which errors Jameson experienced, but sometimes I have to
use LD_PRELOADed 32bit libraries with some software and when I
accidentally run my emacs (which is 64bit) with LD_PRELOAD set this way,
every execution of notmuch prints
ERROR: ld.so: object '/opt/xilinx/usb-driver/libusb-driver.so' from LD_PRELOAD cannot be preloaded: ignored.
and this breaks the parsing. So thanks Jameson for solving this issue
for me.
-Michal
next prev parent reply other threads:[~2011-01-27 11:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 20:57 [PATCH] emacs: send notmuch-query stderr to /dev/null Jameson Rollins
2011-01-27 4:49 ` Carl Worth
2011-01-27 11:29 ` Michal Sojka [this message]
2011-01-28 0:04 ` Jameson Rollins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zkqm7fge.fsf@steelpick.2x.cz \
--to=sojkam1@fel.cvut.cz \
--cc=cworth@cworth.org \
--cc=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).