From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [PATCH 0/5] Rework url-retrieve-synchronously wrapper
Date: Sun, 23 May 2021 17:46:18 -0400 [thread overview]
Message-ID: <20210523214623.31331-1-kyle@kyleam.com> (raw)
The main change is in the second patch, which brings piem's
url-retrieve-synchronously wrapper closer to url-insert-file-contents.
The other patches are small tweaks and cleanups in related code.
Note that this involves the removal of two functions,
piem-download-and-decompress and piem-check-gunzip. I'd be surprised
if there are any outside callers at this point, but either way I don't
plan to add backward-compatibility kludges at this stage in
development.
[1/5] b4: Check for message ID match when using current buffer's URL
[2/5] Rework url-retrieve-synchronously wrapper
[3/5] piem-gunzip-buffer: Check for gunzip executable
[4/5] piem-gunzip-buffer: Absorb caching of gunzip check
[5/5] piem-gunzip-buffer: Don't assume t.mbox.gz is being decompressed
piem-b4.el | 18 +++++-----
piem.el | 104 ++++++++++++++++++++++++++---------------------------
2 files changed, 60 insertions(+), 62 deletions(-)
base-commit: 2333819ee6b632909ba7333eb61be1653f5d8203
--
2.31.1
next reply other threads:[~2021-05-23 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 21:46 Kyle Meyer [this message]
2021-05-23 21:46 ` [PATCH 1/5] b4: Check for message ID match when using current buffer's URL Kyle Meyer
2021-05-23 21:46 ` [PATCH 2/5] Rework url-retrieve-synchronously wrapper Kyle Meyer
2021-05-23 21:46 ` [PATCH 3/5] piem-gunzip-buffer: Check for gunzip executable Kyle Meyer
2021-05-23 21:46 ` [PATCH 4/5] piem-gunzip-buffer: Absorb caching of gunzip check Kyle Meyer
2021-05-23 21:46 ` [PATCH 5/5] piem-gunzip-buffer: Don't assume t.mbox.gz is being decompressed 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=20210523214623.31331-1-kyle@kyleam.com \
--to=kyle@kyleam.com \
--cc=piem@inbox.kyleam.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.kyleam.com/piem/
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).