From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: Displaying picture from PGP key if present?
Date: Wed, 26 Dec 2012 01:33:33 +0100 [thread overview]
Message-ID: <87ip7py7mq.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87obhhybna.fsf@topper.koldfront.dk>
On Wed, 26 Dec 2012 00:06:49 +0100, Adam wrote:
>> Also, the created file should be cleaned up somehow.
> Good point. That should only be a (delete-file filename) away.
(No; it seems that create-image doesn't actually read the file, so
deleting it right after that doesn't work.)
>> You should probably use --attribute-fd instead of letting gpg export
>> the image to a file.
From my experimenting it seems that I can't get just the image out on
the --attribute-fd I give - I get 16 bytes more than the image; and this
in the terminal:
[GNUPG:] ATTRIBUTE 1659209319D5C06ED3203A201D27DB4BA94B3003 2686 1 1 1 1194925497 0 0
which does not seem helpful; especially as I can't find any explanation
of what the different stuff means (second number is the length, first is
they key I am listing).
So, I'm kind of stuck on that.
Then I tried this to avoid the temporary file in this way:
(defun my-epg-key-image (key-id)
"Return the image of a key, if any"
(let* ((coding-system-for-write 'binary)
(coding-system-for-read 'binary)
(data (shell-command-to-string (concat epg-gpg-program
" --list-options show-photos"
" --photo-viewer 'cat - >&2'"
" --list-keys " key-id " >/dev/null"))))
(when (> (length data) 0)
(create-image data nil t))))
but for some reason the resulting image is just a white square. I guess
there is some encoding/uni/multibyte thing I'm missing.
Hm. Maybe I should just skip the first 16 bytes when using --attribute-fd...
Best regards,
Adam
--
"A distributed system is one in which the failure of Adam Sjøgren
a computer you didn't even know existed can render asjo@koldfront.dk
your own computer unusable."
next prev parent reply other threads:[~2012-12-26 0:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 14:12 Adam Sjøgren
2012-12-25 11:43 ` Lars Ingebrigtsen
2012-12-25 11:51 ` Adam Sjøgren
2012-12-25 12:00 ` Lars Ingebrigtsen
2012-12-25 12:05 ` Adam Sjøgren
2012-12-25 12:20 ` Lars Ingebrigtsen
2012-12-25 13:20 ` Adam Sjøgren
2012-12-25 13:47 ` Lars Ingebrigtsen
2012-12-25 22:33 ` Adam Sjøgren
2012-12-25 22:38 ` Adam Sjøgren
2012-12-25 22:43 ` Lars Ingebrigtsen
2012-12-25 22:57 ` Andreas Schwab
2012-12-25 23:06 ` Adam Sjøgren
2012-12-26 0:33 ` Adam Sjøgren [this message]
2012-12-26 1:12 ` Adam Sjøgren
2012-12-26 5:44 ` Daiki Ueno
2012-12-26 13:24 ` Adam Sjøgren
2012-12-27 5:16 ` Arne Jørgensen
2012-12-28 21:00 ` Adam Sjøgren
2012-12-28 21:03 ` Adam Sjøgren
2012-12-28 21:09 ` Adam Sjøgren
2012-12-28 22:04 ` Arne Jørgensen
2012-12-28 22:06 ` Adam Sjøgren
2012-12-27 10:06 ` Julien Danjou
2012-12-27 10:38 ` Andreas Schwab
2012-12-27 12:12 ` Adam Sjøgren
2013-02-25 7:19 ` Binjo
2013-02-25 19:13 ` Adam Sjøgren
2013-02-26 2:22 ` Binjo
2013-02-26 19:28 ` Adam Sjøgren
2013-02-27 2:27 ` Binjo
2012-12-26 9:14 ` Andreas Schwab
2012-12-26 13:17 ` Adam Sjøgren
2012-12-26 18:05 ` Andreas Schwab
2012-12-26 22:06 ` Adam Sjøgren
2012-12-26 4:22 ` Daiki Ueno
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=87ip7py7mq.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.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).