From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: [emacs] handle unexpected stderr output from notmuch command
Date: Sun, 14 Apr 2024 11:29:53 -0300 [thread overview]
Message-ID: <87r0f83tlq.fsf@tethera.net> (raw)
TIL that the running the notmuch command from inside "proxychains4
emacs", generates unexpected output on stderr, which messes up various
emacs commands. This can be worked around by running "proxychains4 -q
emacs", but it would be nice to handle output on stderr more
consistently. I got as far as localizing the bug in
notmuch-command-to-string.
PS. Now you see why we went such effort not to have the notmuch library
print to stderr.
reply other threads:[~2024-04-14 14:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87r0f83tlq.fsf@tethera.net \
--to=david@tethera.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).