discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [PATCH 0/4] Support reading inboxes from ~/.public-inbox/config
Date: Thu, 10 Jun 2021 14:59:39 -0400	[thread overview]
Message-ID: <20210610185943.14155-1-kyle@kyleam.com> (raw)

There's a longstanding to-do comment above piem-inboxes about adding
support for collecting information from ~/.public-inbox/config.  The
last patch implements that feature.  The first two patches fix minor
piem-inbox-coderepo{,-maybe-read} issues that I spotted while working
on the tests.

  [1/4] piem-inbox-coderepo-maybe-read: Avoid confusing "inbox" references
  [2/4] piem-inbox-coderepo*: Always return coderepo as a directory
  [3/4] piem-inboxes: Clarify that :coderepo points to a working tree
  [4/4] Support reading inboxes from ~/.public-inbox/config

 Documentation/piem.texi   |  56 ++++++++++--
 piem-b4.el                |  12 +--
 piem-notmuch.el           |  10 ++-
 piem.el                   | 180 +++++++++++++++++++++++++++++++++-----
 tests/piem-rmail-tests.el |   6 +-
 tests/piem-tests.el       |  70 ++++++++++++++-
 6 files changed, 294 insertions(+), 40 deletions(-)

base-commit: 990c3f3b098074945673842e2ecb351832f61402

             reply	other threads:[~2021-06-10 18:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 18:59 Kyle Meyer [this message]
2021-06-10 18:59 ` [PATCH 1/4] piem-inbox-coderepo-maybe-read: Avoid confusing "inbox" references Kyle Meyer
2021-06-10 18:59 ` [PATCH 2/4] piem-inbox-coderepo*: Always return coderepo as a directory Kyle Meyer
2021-06-10 18:59 ` [PATCH 3/4] piem-inboxes: Clarify that :coderepo points to a working tree Kyle Meyer
2021-06-10 18:59 ` [PATCH 4/4] Support reading inboxes from ~/.public-inbox/config Kyle Meyer
2021-06-10 19:32   ` Xinglu Chen
2021-06-10 21:00     ` Kyle Meyer

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:

  List information: https://git.kyleam.com/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210610185943.14155-1-kyle@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \


* 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


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).