unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Mark Walters <markwalters1009@gmail.com>,
	Adam Wolfe Gordon <awg+notmuch@xvx.ca>,
	notmuch@notmuchmail.org
Subject: Re: [PATCH 0/3] Introduce the add command
Date: Sun, 21 Jul 2013 13:25:31 -0700	[thread overview]
Message-ID: <87bo5vu0ck.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87r4es8h0p.fsf@qmul.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

On Sun, Jul 21 2013, Mark Walters <markwalters1009@gmail.com> wrote:
> I sort of agree but wonder if it would be more natural under "new" than
> "insert". so notmuch new /path/to/file just adds that file (provided it
> is in the database; perhaps a relative path?) This would also be
> extensible to do a whole mail sub-directory which seems like it might
> also be a useful feature. (I am definitely not saying that this needs to
> be implemented now!)

Oh, yeah, good call.  That definitely seems more natural to me as well.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2013-07-21 20:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-14  0:45 [PATCH 0/3] Introduce the add command Adam Wolfe Gordon
2013-07-14  0:45 ` [PATCH 1/3] cli: Return an error code from add_message_to_database Adam Wolfe Gordon
2013-07-14  0:45 ` [PATCH 2/3] cli: Introduce the add command Adam Wolfe Gordon
2013-07-14  0:45 ` [PATCH 3/3] test: Add simple tests for " Adam Wolfe Gordon
2013-07-17 15:23 ` [PATCH 0/3] Introduce " Tomi Ollila
2013-07-19 14:48 ` Jameson Graef Rollins
2013-07-21  8:16   ` Mark Walters
2013-07-21 20:25     ` Jameson Graef Rollins [this message]
2013-07-21 21:47     ` Vladimir Marek

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=87bo5vu0ck.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=awg+notmuch@xvx.ca \
    --cc=markwalters1009@gmail.com \
    --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).