diff options
| author | Kyle Meyer <kyle@kyleam.com> | 2021-06-10 14:59:43 -0400 |
|---|---|---|
| committer | Kyle Meyer <kyle@kyleam.com> | 2021-06-11 13:36:54 -0400 |
| commit | c901d3ec025773c8eae04257099fcdfe704085ac (patch) | |
| tree | 738fb967fe89d468e5a5d8f56810c544bd9075bd /piem-b4.el | |
| parent | 61952fe189a2a1e97b7156eaee831a5a1915dd57 (diff) | |
| download | piem-c901d3ec025773c8eae04257099fcdfe704085ac.tar.gz | |
Support reading inboxes from ~/.public-inbox/config
A client may mirror and configure inboxes locally. Doing so enables
fast local access to public-inbox-httpd and public-inbox-nntpd. And
with the next pubic-inbox release (v1.7), it will be necessary to set
up local externals for lei.
That can lead to a good amount of information being duplicated between
the piem-inboxes option and ~/.public-inbox/config. To avoid this,
let users set an option to enable collecting information from
public-inbox's configuration.
This relies on code getting the list of inboxes with
piem-merged-inboxes rather than inspecting piem-inboxes directly.
That should be okay because at this point there should be very few
third-party callers. An alternative would be to merge values from the
configuration into the value of piem-inboxes. That'd let callers
continue to inspect public-inboxes, but I'd prefer not to touch the
value of a user option.
Message-Id: <20210610185943.14155-5-kyle@kyleam.com>
Diffstat (limited to 'piem-b4.el')
| -rw-r--r-- | piem-b4.el | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -69,8 +69,8 @@ This is intended to be used for debugging purposes.") (unless (= (point-max) 1) (setq local-mbox-p t)))) ;; `piem-mid-to-thread-functions' didn't generate an mbox. Next - ;; try to download it from a URL at `piem-inboxes'. Finally, fall - ;; back to b4's configuration. + ;; try to download it from an inbox's URL. Finally, fall back to + ;; b4's configuration. (unless local-mbox-p (when-let ((url (and (equal mid (piem-mid)) (piem-inbox-get :url)))) @@ -133,10 +133,10 @@ list of arguments specified via ARGS." Try to generate a thread for the Message-Id MID with `piem-mid-to-thread-functions'. If that fails, try to download -the thread from the `piem-inboxes' URL associated with the -current buffer, provided that the current buffer's message ID -matches MID. And if that doesn't work, let `b4 am' download the -thread according to its own configuration. +the thread from an inbox URL associated with the current buffer, +provided that the current buffer's message ID matches MID. And +if that doesn't work, let `b4 am' download the thread according +to its own configuration. After calling `b4 am' with ARGS to prepare an am-ready mbox, feed the result to `git am'. |