From: David Bremner <david@tethera.net>
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: Helpers for notmuch developers.
Date: Thu, 05 Jan 2012 23:39:30 -0400 [thread overview]
Message-ID: <878vllxzwt.fsf@zancas.localnet> (raw)
In-Reply-To: <1325685678-12710-1-git-send-email-dme@dme.org>
On Wed, 4 Jan 2012 14:01:18 +0000, David Edmondson <dme@dme.org> wrote:
> ---
>
> I've been using this for a few days and decided to share it to get
> feedback. Reviewing patches can be tedious, so I tried to make things
> a little simpler.
>
I didn't have a very thorough look at the code, but I like the
functionality. Especially hitting q a few times from magit and being in
the right place to reply.
> General management (i.e. keeping up to date) of the repository it uses
> is your responsibility, as is cleaning out old branches. You can, of
> course, just delete the temporary repository after using it - the code
> will re-create it next time.
maybe the branches could be under some namespace that makes this easy?
> +(defvar notmuch-dev-temporary-repository-name (concat "notmuch-dev-" (user-login-name))
> + "The name of the temporary repository.")
Do we care about security at all in this context? I'm always a bit
nervous about creating predictably named files/directories in publicly
writable places.
> + ;; Causes us to switch to the magit buffer - is that unfortunate in
> + ;; some situations?
> + (magit-status notmuch-dev-temporary-repository-path))
I found it to be a pleasant surprise.
> + (shell-command
> + (concat
> + notmuch-command " show --format=mbox " (shell-quote-argument search-terms)
> + " | "
> + "git am --quiet"))
> +
Hmm. A knee jerk reaction is not to like this, like seeing system in C
code. But I don't have a better solution off hand.
d
next prev parent reply other threads:[~2012-01-06 3:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 14:01 [PATCH] emacs: Helpers for notmuch developers David Edmondson
2012-01-06 3:39 ` David Bremner [this message]
2012-01-06 8:27 ` David Edmondson
2012-01-06 10:03 ` [PATCH v2] " David Edmondson
2012-01-07 11:53 ` David Bremner
2012-01-09 8:23 ` David Edmondson
2012-01-09 10:38 ` David Bremner
2012-01-09 11:16 ` David Edmondson
2012-01-13 3:04 ` David Bremner
2012-01-13 10:25 ` [PATCH] notmuch-dev: Forcibly delete branches David Edmondson
2012-01-13 12:25 ` David Bremner
2012-01-13 13:28 ` [PATCH 1/2] notmuch-dev: Remove more characters from branch names David Edmondson
2012-01-13 13:28 ` [PATCH 2/2] notmuch-dev: Update the master branch when requested David Edmondson
2012-01-13 21:03 ` Xavier Maillard
2012-01-16 9:07 ` David Edmondson
2012-01-16 21:19 ` Xavier Maillard
2012-01-06 22:56 ` [PATCH] emacs: Helpers for notmuch developers Tomi Ollila
2012-01-09 8:27 ` David Edmondson
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=878vllxzwt.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=dme@dme.org \
--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).