From: William Casarin <jb55@jb55.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Cc: Jonas Bernoulli <jonas@bernoul.li>, Teemu Likonen <tlikonen@iki.fi>
Subject: Re: [PATCH] NEWS: add news entry for tree navigation changes
Date: Sun, 23 Aug 2020 09:38:49 -0700 [thread overview]
Message-ID: <875z99fhba.fsf@jb55.com> (raw)
In-Reply-To: <871rjxegrj.fsf@tethera.net>
David Bremner <david@tethera.net> writes:
> William Casarin <jb55@jb55.com> writes:
>
>> Signed-off-by: William Casarin <jb55@jb55.com>
>> ---
>> NEWS | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>
> Applied to master and release, with a tiny wording change.
>
> I realized when looking at this that I had completely forgotten
> notmuch-tree-from-search-thread. I suspect some of emacs interface is
> not as discoverable as we think it is
Indeed, I only discovered this function after Teemu mentioned[1] it in a
mailing list thread. I've always like the magit docs, maybe we can get
to something like that eventually.
[1] id:87pnhxceoy.fsf@iki.fi
The elisp code has plenty of comments that document each function,
perhaps there could be a way to generate documentation from that? Not
sure how magit does it.
> and it would be worth updating
> (not for the upcoming release, but afterwards) doc/notmuch-emacs.rst
> with some of the nifty features that have been added since I
> optimistically wrote (eb6fb36d)
>
> This is pretty minimal, but will hopefully inspire others to
> contribute more complete documentation
Oh good to know! Didn't realize this was a thing.
Cheers,
Will
next prev parent reply other threads:[~2020-08-23 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <id:87k0xqg7c7.fsf@tethera.net>
2020-08-22 18:05 ` [PATCH] NEWS: add news entry for tree navigation changes William Casarin
2020-08-23 11:36 ` David Bremner
2020-08-23 16:38 ` William Casarin [this message]
2020-08-23 19:43 ` 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=875z99fhba.fsf@jb55.com \
--to=jb55@jb55.com \
--cc=david@tethera.net \
--cc=jonas@bernoul.li \
--cc=notmuch@notmuchmail.org \
--cc=tlikonen@iki.fi \
/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).