unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH 2/2] emacs: Allow tagging regions in notmuch-tree
Date: Sat, 25 May 2019 13:41:22 +0200	[thread overview]
Message-ID: <87woieoj6l.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87v9xyn5vu.fsf@tethera.net>

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

David Bremner <david@tethera.net> writes:

>> --8<---------------cut here---------------start------------->8---
>>> guix environment notmuch -- /home/ambrevar/.local/share/emacs/site-lisp/notmuch/test/T460-emacs-tree.sh
>> guix environment: error: execlp: No such file or directory: "/home/ambrevar/.local/share/emacs/site-lisp/notmuch/test/T460-emacs-tree.sh"
>> --8<---------------cut here---------------end--------------->8---
>
> I can't really help you with Guix, but I suggest setting up some
> environment where you can run things in an interactive shell.
>
> In particular that error seems to be claiming the test file doesn't
> exist, which would be easy to debug in an interactive shell.

Yup, that's what I did with "guix environment notmuch": it sets up a
build environment (and an interactive shell) for notmuch.  And I really
wonder why it can't find the file, it's there in the interactive shell.
It's possible that the error message is a red herring though, I'll look
into it.

> For better or for worse, our standards are higher for new code. Since
> (as you have just observed) minor style problems in existing code tend
> to linger unfixed.

So would you like me to patch the namespacing along with these changes
or leave it for another patch?

> I assume you are not using git-send-email because it's difficult for
> you; it's not that a big of a deal, although we do prefer series
> generated git-send-email for reviewing.

I'm using git-send-email on a regular basis, no problem with that.  (I
wonder why you would think it's difficult for me :p)

git-send-email comes with different workflows though, I'm not sure which
one Notmuch follows.  Do you prefer versioned patch series
(e.g. [PATCHv2], etc.) or patch updates sent with
"--in-reply-to=<message-id-of-the-last-email>"?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-05-25 11:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 16:47 [PATCH 1/2] emacs: Move notmuch-search-interactive-region to notmuch-lib as notmuch-interactive-region Pierre Neidhardt
2019-04-09 16:47 ` [PATCH 2/2] emacs: Allow tagging regions in notmuch-tree Pierre Neidhardt
2019-05-08 11:00   ` David Bremner
2019-05-14 10:40     ` Pierre Neidhardt
2019-05-25 11:13       ` David Bremner
2019-05-25 11:41         ` Pierre Neidhardt [this message]
2019-05-25 13:42           ` David Bremner
2019-05-07  9:35 ` [PATCH 1/2] emacs: Move notmuch-search-interactive-region to notmuch-lib as notmuch-interactive-region David Bremner
2019-05-20 12:35   ` Leo Vivier
2019-05-20 17:11     ` Tomi Ollila
2019-05-22 14:56       ` Leo Vivier
2019-05-23 11:14         ` David Bremner
2019-05-23 11:19           ` Leo Vivier
2019-05-23 17:07             ` 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=87woieoj6l.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --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).