feat: move mblog header handling into mime4cl
Accessing the headers of a MIME message feels like something mime4cl should handle. We implemented this ad hoc in mblog before in order to not need to worry about doing it in a sensible way. Now we introduce a decent-ish interface for getting a header from a MIME message, mime-message-header-values: * It returns a list because MIME message headers may appear multiple times. * It decodes RFC2047 only upon request, as you may want to be stricter about parsing certain fields. * It checks header name equality case insensitively. The code for decoding the RFC2047 string is retained and still uses babel for doing the actual decoding. Change-Id: I58bbbe4b46dbded04160b481a28a40d14775673d Reviewed-on: https://cl.tvl.fyi/c/depot/+/5150 Tested-by: BuildkiteCI Reviewed-by: sterni <sternenseemann@systemli.org>
This commit is contained in:
parent
81c47da91c
commit
5bc73de59d
7 changed files with 43 additions and 37 deletions
1
third_party/lisp/mime4cl/default.nix
vendored
1
third_party/lisp/mime4cl/default.nix
vendored
|
|
@ -6,6 +6,7 @@ depot.nix.buildLisp.library {
|
|||
name = "mime4cl";
|
||||
|
||||
deps = [
|
||||
depot.third_party.lisp.babel
|
||||
depot.third_party.lisp.sclf
|
||||
depot.third_party.lisp.npg
|
||||
depot.third_party.lisp.trivial-gray-streams
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue