discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [PATCH] Add a very incomplete to-do list
Date: Thu, 10 Jun 2021 20:20:40 -0400	[thread overview]
Message-ID: <20210611002040.4709-1-kyle@kyleam.com> (raw)

Transplant some items from my private to-do list to hopefully give
others a better sense for what's planned.
 TODO | 44 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 44 insertions(+)
 create mode 100644 TODO

diff --git a/TODO b/TODO
new file mode 100644
index 00000000..94ecd8d5
--- /dev/null
+++ b/TODO
@@ -0,0 +1,44 @@
+A (sparse and likely stale) to-do list for piem                   -*-outline-*-
+* general
+** piem-inboxes: support mapping inbox to multiple coderepos
+A catchall inbox may be used for small projects without a dedicated
+** "report inbox" command for debugging
+** "show message ID at point" command
+Should have ability to extract message ID from link (like lei-lcat)
+and give priority to local sources.
+* b4
+** add transients for other b4 subcommands?
+Only `mbox' and `am' are supported at the moment.
+** piem-b4-am-from-mid: option for local-only operation
+A caller that relies on piem-mid-to-thread-functions to produce a
+thread may not have the URL in piem-inboxes set or b4 configured.
+* lei
+** history and locking for query and show buffers
+** label/keyword support
+See <https://public-inbox.org/meta/20210224204950.GA2076@dcvr> and
+** more efficient handling of remote operations
+** saved searches
+** show: attachment handling
+** show: highlight diffs
+** show: support replying
+** transients for some other lei commands
+** transient wrapper around piem-lei-query

base-commit: 990c3f3b098074945673842e2ecb351832f61402

                 reply	other threads:[~2021-06-11  0:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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