discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [ANNOUNCE] piem v0.3.0
Date: Fri, 05 Nov 2021 21:59:21 -0400	[thread overview]
Message-ID: <87a6ii6o3q.fsf@kyleam.com> (raw)

piem v0.3.0 has been released, with a corresponding tag pushed to
<https://git.kyleam.com/piem/>.  It consists of 54 non-merge commits
since v0.2.0 contributed by Kyle Meyer and Xinglu Chen.

Bug reports, patches, questions, and other feedback are welcome.  Please
send a plain-text email to


Messages that include this address are public and available as
public-inbox archives at



piem v0.3.0 release notes

Changes since v0.2.0

 * Which directory piem-inject-thread-into-maildir uses can now be
   configured per-project via the :maildir keyword in a project's
   piem-inboxes entry.

 * piem-inboxes can be populated from ~/.public-inbox/config, which is
   useful for those that mirror inboxes locally (e.g., for fast
   public-inbox-httpd or public-inbox-nttpd access or for use with
   public-inbox's new lei command).

 * The b4-am transient learned some new options, keeping up with
   upstream changes in b4.

 * piem-use-magit is no longer set to nil when piem is loaded before
   Magit.  Users that want to disable Magit support even though it's
   available and loaded on their system must explicitly set
   piem-use-magit to nil.

 * New library piem-lei.el provides undocumented, incomplete, and
   experimental support for public-inbox's 'lei q' command (added in
   public-inbox v1.7).

 * New library piem-rmail.el provides basic Rmail integration.

 * The documentation describing how piem-b4-am-ready-from-mid gets a
   message ID's thread has been improved.

 * The documentation now specifies that the :coderepo keyword of
   piem-inboxes should point to a working tree, unlike public-inbox's

Fixes since v0.2.0

 * piem-b4-am-from-mid assumed that, if the buffer at point is
   associated with an inbox, its message ID matches the target message
   ID, which may not be the case for non-interactive calls.


Kyle Meyer (53):
      piem-use-magit: Reword docstring to clarify scope
      piem-use-magit: Unconditionally set to t
      b4: Check for message ID match when using current buffer's URL
      Rework url-retrieve-synchronously wrapper
      piem-gunzip-buffer: Check for gunzip executable
      piem-gunzip-buffer: Absorb caching of gunzip check
      piem-gunzip-buffer: Don't assume t.mbox.gz is being decompressed
      b4: Better describe how piem-b4-am-ready-from-mid gets the thread
      Add basic integration for Rmail
      piem.el: Drop an empty line
      lei: Add command and mode for displaying a message
      piem-lei-show: Let caller suppress displaying buffer
      piem-lei-show: Highlight headers and quoted text
      lei: Add command and mode for displaying overview of search results
      lei query: Add piem-lei-show wrapper for displaying line's message
      lei: Add command for viewing a thread
      lei query: Fontify results
      piem-lei-query-thread: Position point on seed message
      piem-lei-query-thread: Drop repeated subjects
      piem-lei-query-thread: Deal with multiple "re:"s
      piem-lei-query-thread: Omit main part of subject if shared
      piem-lei-query-thread: Add bug#NNN special case when eliding subject
      lei query: Add next/previous line variants that update message buffer
      piem-lei-show: Record message ID
      lei query: Add commands for showing or scrolling message buffer
      lei: Configure bindings for query and show modes
      lei: Wire up piem.el hooks
      piem-lei-query-thread: Use piem-lei-get-mid to get message ID
      piem-inboxes: Fix typo in comment
      manual: Avoid space between link and closing parenthesis
      Add a very incomplete to-do list
      piem-lei-query-mode: Highlight current line
      piem-b4-am: Specify :man-page
      piem-inbox-coderepo-maybe-read: Avoid confusing "inbox" references
      piem-inbox-coderepo*: Always return coderepo as a directory
      piem-inboxes: Clarify that :coderepo points to a working tree
      Support reading inboxes from ~/.public-inbox/config
      Prefer mail-decode-encoded-word-string to rfc2047-decode-string
      b4-am: Fill in more options
      piem-notmuch-known-mid-p: Autoload
      lei: Prefer "mid:" to "m:"
      piem-notmuch-known-mid-p: Drop call to with-current-buffer
      piem-lei-query-show: Fix capitalization in error message
      piem-lei-known-mid-p: Use with-output-to-string
      lei: Introduce option to set "lei" executable
      lei: Add call-process wrapper for inserting lei output
      piem-lei-insert-output: Signal an error if lei call fails
      lei: Add transient wrapper for piem-lei-query
      lei: Set piem-lei-buffer-query for mid-based query functions
      piem: Add function that returns public-inbox's configuration file
      lei q: Offer candidates for --include and --only
      lei: Rename piem-lei-show-mid to piem-lei-buffer-mid
      Release version 0.3.0

Xinglu Chen (1):
      piem: Add :maildir keyword to piem-inboxes

                 reply	other threads:[~2021-11-06  1:59 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=87a6ii6o3q.fsf@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).