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

Pierre Neidhardt <mail@ambrevar.xyz> writes:

Thanks for the updated patches.

>
>> 3) We generally want at least one test for a new
>>    feature. test/T460-emacs-tree.sh has the existing tree related
>>    tests. Again, if you need help with the test suite, let us know.
>
> I've added a test, but I wasn't able to run it on Guix
> (https://guix.info).  It fails like this:
>
> --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.

>
>> 4) Please use notmuch-tree-- as a prefix for new private symbols that
>>    users should not rely on. I'm not sure about which symbols that applies
>>    to here.
>
> I've mirrored the implementation of search-mode.
> There are indeed a few functions that are only used locally, but so are
> they in notmuch.el, so I guess this should be part of another patch.
>

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.

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.

  reply	other threads:[~2019-05-25 11:13 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 [this message]
2019-05-25 11:41         ` Pierre Neidhardt
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=87v9xyn5vu.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=mail@ambrevar.xyz \
    --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).