unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: sanitization of args notmuch-cli in notmuch-emacs
Date: Tue, 04 Feb 2014 20:02:01 +0200	[thread overview]
Message-ID: <m2ppn2ycx2.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <87mwi7uip0.fsf@maritornes.cs.unb.ca>

On Tue, Feb 04 2014, David Bremner <david@tethera.net> wrote:

> Tomi Ollila <tomi.ollila@iki.fi> writes:
>
>>
>> Maybe the cli should be fixed ? (and/or make emacs MUA resilient to
>> this kind of result)
>>
>
> Would it make any sense to output errors in structured format?  I guess
> the downside is it would be harder for a human user to read.

notmuch count --batch outputs just numbers separated by newline -- and
with emacs stdout & stderr are in the same stream (in this case too)
For that we'd need structured like notmuch count --batch --format=sexp
and then write errors there...

I don't think we can find SomeOne(tm) to do this -- or the überversion
like 'notmuch execute' which takes sexp/json document in stdin and
spits out sexp/json document for programs to parse ;D

> d

Romi

  parent reply	other threads:[~2014-02-04 18:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 19:13 sanitization of args notmuch-cli in notmuch-emacs David Bremner
2014-02-03 20:36 ` Tomi Ollila
2014-02-03 21:21   ` Tomi Ollila
2014-02-08 14:25     ` [PATCH] emacs: remove newlines from input to notmuch count --batch David Bremner
2014-02-08 18:31       ` Tomi Ollila
2014-02-26  1:02       ` David Bremner
2014-02-04 13:10   ` sanitization of args notmuch-cli in notmuch-emacs David Bremner
2014-02-04 17:30     ` Mark Walters
2014-02-04 18:02     ` Tomi Ollila [this message]
2014-02-26  1:03 ` David Bremner

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=m2ppn2ycx2.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --cc=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).