diff options
| author | Kyle Meyer <kyle@kyleam.com> | 2023-04-30 18:15:49 -0400 |
|---|---|---|
| committer | Kyle Meyer <kyle@kyleam.com> | 2023-04-30 20:25:46 -0400 |
| commit | 2c37ca5e9a1b5f63e4cfe24c221602cf2eb03e0e (patch) | |
| tree | 1fec337fdd2c19419bc45dcaa829f6ee7a7246a8 | |
| parent | d78900f06615e247cee5472beca4e7ae164fe77f (diff) | |
| download | piem-2c37ca5e9a1b5f63e4cfe24c221602cf2eb03e0e.tar.gz | |
piem-b4-am-from-mid: Tweak docstring for consistency
MID is used throughout the code base, and what it refers to is
probably clear enough without putting "Message-Id" in front of it.
(If it were to stay, it should probably be spelled "message ID").
Message-ID: <20230430221552.251335-2-kyle@kyleam.com>
| -rw-r--r-- | piem-b4.el | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -131,7 +131,7 @@ list of arguments specified via ARGS." (defun piem-b4-am-from-mid (mid &optional args toggle-worktree) "Get the thread for MID, extract an am-ready mbox, and apply it. -Try to generate a thread for the Message-Id MID with +Try to generate a thread for MID with `piem-mid-to-thread-functions'. If that fails, try to download the thread from an inbox URL associated with the current buffer, provided that the current buffer's message ID matches MID. And |