From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Handling of encrypted PGP/MIME multipart messages
Date: Sat, 23 May 2020 15:35:57 +0200 [thread overview]
Message-ID: <20200523133557.qTlORS6yPXE9Bz1kA8KdHJ9Kf-0d_gknPEIiHPJXrIA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-175@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
New comment by leahneukirchen on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/175#issuecomment-633055063
Comment:
Reopening this. I looked into using filters for mshow -t and -x, but it seems like a waste to run them just because of the exit status.
Perhaps mgpg should just be integrated into mshow directly (and spawn gpg via a pipe).
Patches welcome.
next prev parent reply other threads:[~2020-05-23 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 19:53 [ISSUE] " nmeum
2020-05-16 20:03 ` leahneukirchen
2020-05-16 20:05 ` leahneukirchen
2020-05-17 8:34 ` [ISSUE] [CLOSED] " nmeum
2020-05-23 13:35 ` leahneukirchen [this message]
2020-05-23 15:10 ` nmeum
2023-02-12 13:13 ` xelxebar
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200523133557.qTlORS6yPXE9Bz1kA8KdHJ9Kf-0d_gknPEIiHPJXrIA@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).