From: Jesse Rosenthal <jrosenthal@jhu.edu>
To: Austin Clements <amdragon@MIT.EDU>
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: Replacing my name/email with "me" (or similar) in author lists
Date: Thu, 01 Mar 2012 09:28:19 -0500 [thread overview]
Message-ID: <87y5rkxunw.fsf@jhu.edu> (raw)
In-Reply-To: <87k435ntnx.fsf@awakening.csail.mit.edu>
On Wed, 29 Feb 2012 17:47:46 -0500, Austin Clements <amdragon@MIT.EDU> wrote:
> > On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements <amdragon@MIT.EDU> wrote:
> > > What if the output of search (say, specifically the JSON format)
> > > included information on each message in the thread such as the
> > > 'message' production from devel/schemata minus the body field?
> [...]
> I was suggesting just using notmuch_thread_get_toplevel_messages in
> search (essentially, mixing a bit of show into search). No library
> changes necessary.
In any event, I'd really love to see something like this. Because I work
remotely, over an ssh tunnel, and it's nice to have various scripts
local. However, things like notmuch_addresses and my recipient_search
script have to run on the server, since they need bindings-level access
to the database. If I could get the JSON you describe over the wire, I
could probably just make one remote call and then confine my local work
to JSON parsing. A niche need, I realize.
prev parent reply other threads:[~2012-03-01 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 16:34 Replacing my name/email with "me" (or similar) in author lists Daniel
2012-02-26 11:22 ` Patrick Totzke
2012-02-26 16:41 ` Daniel Schoepe
2012-02-26 16:51 ` David Bremner
2012-02-26 21:59 ` Tom Prince
2012-02-29 15:05 ` Jesse Rosenthal
2012-02-29 15:36 ` Austin Clements
2012-02-29 15:50 ` Jesse Rosenthal
2012-02-29 22:47 ` Austin Clements
2012-03-01 14:28 ` Jesse Rosenthal [this message]
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=87y5rkxunw.fsf@jhu.edu \
--to=jrosenthal@jhu.edu \
--cc=amdragon@MIT.EDU \
--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).