From c99e806fd307ef69adc0d3a277385687edfd3454 Mon Sep 17 00:00:00 2001 From: Kyle Meyer Date: Sun, 23 May 2021 20:50:40 -0400 Subject: b4: Better describe how piem-b4-am-ready-from-mid gets the thread piem-b4-am-ready-from-mid's docstring doesn't mention that it tries to download the thread from a piem-inboxes URL before falling back to letting b4 handle the download. The manual's description is better, though it makes it sound like the b4 fallback depends on not finding a URL in piem-inboxes rather than the download being unsuccessful for whatever reason. Reword the docstring and manual text to hopefully make things clearer. Message-Id: <20210524005040.12668-1-kyle@kyleam.com> --- Documentation/piem.texi | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'Documentation') diff --git a/Documentation/piem.texi b/Documentation/piem.texi index ca6a97b..f4bbabc 100644 --- a/Documentation/piem.texi +++ b/Documentation/piem.texi @@ -341,11 +341,11 @@ a non-nil value or by giving a prefix argument. To generate the input thread, first any functions in @code{piem-mid-to-thread-functions} are tried. This allows for a thread to be retrieved from a local store (e.g., the Notmuch database). If -that fails, the thread is downloaded from the public-inbox URL -associated with the current buffer. Finally, if an inbox's entry in -@code{piem-inboxes} doesn't specify a URL, @code{b4 am} is called -without a local mbox, letting it download the thread according to its -own configuration. +that fails, try to download the thread from the @code{piem-inboxes} URL +associated with the current buffer, provided the current buffer's +message ID matches the one @code{piem-b4-am-from-mid} was called with. +As a last resort, call @code{b4 am} without a local mbox to let it +download the thread according to its own configuration. @item i @itemx M-x piem-b4-am-ready-from-mid -- cgit v1.2.3