From: David Bremner <david@tethera.net>
To: jao <jao@gnu.org>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH v7 1/1] emacs: notmuch-tree-outline-mode
Date: Mon, 12 Dec 2022 09:40:24 -0400 [thread overview]
Message-ID: <87bko8hh9z.fsf@tethera.net> (raw)
In-Reply-To: <87ilih4tf5.fsf@mail.jao.io>
jao <jao@gnu.org> writes:
>>
>> As mentioned in my previous reply, I'm still not 100% clear on why we
>> need both depth and level.
>
> i might be misremembering, but i think depth is just an auxiliarly
> argument taken by that function to know whether it's inserting the tip
> of a tree or not, not a real depth. level is. so a better way would be
> to make 'depth' take the values 'level' is currently taking, but i
> wasn't sure other code would be using depth with its old original
> meaning (e.g. via and advice; i did at some point).
>
depth is used for indentation in notmuch-show-mode, so it should be
(close to) what you want? There is already a function
notmuch-show-get-depth.
>
>>
>>> + (buffer-name notmuch-tree-message-buffer))))
>>
>> At first glance, depending on the buffer name seems fragile?
>
> not sure why, or how to make it more robust...
It depends on the buffer being named after the message-id. If I
understand the current code correctly, this depends on the default
naming in notmuch show, but that could change e.g. like it did for
notmuch-search. OTOH, I guess I don't really understand what this is
checking for, since I was using something based on
#'notmuch-tree-get-message-properties
next prev parent reply other threads:[~2022-12-12 13:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 23:52 [PATCH v7 0/1] emacs: notmuch-tree-outline-mode jao
2022-11-04 23:52 ` [PATCH v7 1/1] " jao
2022-12-04 16:18 ` David Bremner
2022-12-11 18:24 ` David Bremner
2022-12-11 19:44 ` jao
2022-12-12 13:40 ` David Bremner [this message]
2022-12-12 15:22 ` Jose A. Ortega Ruiz
2022-12-12 15:39 ` Jose A. Ortega Ruiz
2022-12-12 16:06 ` David Bremner
2022-12-12 21:06 ` Jose A. Ortega Ruiz
2022-12-13 2:19 ` Jose A. Ortega Ruiz
2022-11-05 0:01 ` [PATCH v7 0/1] " Jonathan Wilner
2022-11-07 17:05 ` Matt Armstrong
2022-11-05 0:09 ` jao
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=87bko8hh9z.fsf@tethera.net \
--to=david@tethera.net \
--cc=jao@gnu.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).