From: Jani Nikula <jani@nikula.org>
To: David Bremner <david@tethera.net>
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: Feature proposal: OUTPUT_AUTHOR format
Date: Tue, 27 Aug 2013 08:21:49 +0300 [thread overview]
Message-ID: <CAB+hUn_YVsGsFo=9qCw_J2VL6t2C1SggyRnZrpP1txQRa7E89g@mail.gmail.com> (raw)
In-Reply-To: <87li3o9dwr.fsf@zancas.localnet>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
On Aug 27, 2013 3:27 AM, "David Bremner" <david@tethera.net> wrote:
>
> Johannes Kulick <johannes@mailless.org> writes:
>
> > An authors output format would not add redundant information to a mail,
would be
> > relatively easy to implement and I would find a people centric view -
which
> > doesn't interfere with any other concept of notmuch - very worth the
couple of
> > new lines of code.
> >
> > What would you say?
>
> Hi Johannes;
>
> I'm not sure I understand your goal completely here, but the obvious
> thing UI wise would be
>
> notmuch search --output=authors --format=(json|text|sexp) $search_terms
>
FWIW, I have some code to this effect that I never posted. I'll see how
much polish it would require.
BR,
Jani.
> Perhaps you're already aware of this, but alot doesn't use the CLI, so
> that wouldn't be directly helpful to having a new view in alot.
>
> d
>
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
[-- Attachment #2: Type: text/html, Size: 1591 bytes --]
next prev parent reply other threads:[~2013-08-27 5:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130825101308.27461.57489@quirm.robotics.tu-berlin.de>
2013-08-26 22:22 ` Feature proposal: OUTPUT_AUTHOR format Johannes Kulick
2013-08-27 0:27 ` David Bremner
2013-08-27 5:21 ` Jani Nikula [this message]
2013-08-27 11:50 ` Johannes Kulick
2013-08-27 13:47 ` Austin Clements
2013-08-27 14:06 ` Johannes Kulick
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='CAB+hUn_YVsGsFo=9qCw_J2VL6t2C1SggyRnZrpP1txQRa7E89g@mail.gmail.com' \
--to=jani@nikula.org \
--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).