From: Gaudenz Steinlin <gaudenz@soziologie.ch>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
Date: Tue, 16 Nov 2010 12:42:33 +0100 [thread overview]
Message-ID: <1289907535-sup-3989@meteor.durcheinandertal.local> (raw)
In-Reply-To: <AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1203 bytes --]
Excerpts from Hamish D's message of Don Nov 11 18:25:13 +0100 2010:
> > - With this patch the output of the gpg run is no longer available.
> > Like this the plus sign in front of the message does not make sense.
> > Is there a way to get at the gpg output with your approach?
>
> The gpg binary is not called, so there is no output from it. What do
> you mean by the "plus sign" - where does this turn up? I haven't
> noticed that. If you tell me exactly what your expected behaviour is
> I'll see if I can replicate it.
The "+" character is right in front of the string "Good signature from
...". If you move the cursor to that line and press enter it changes
to a "-" character, but no additional text is shown. The gpg command
output used to show up there when pressing enter.
I expect there to be some additional output about the signature
validation like keyid, signature date, trust level, ...
At least if you can't provide any additional information, the "+"
character should not show up as this is an indicator that there is
some collapsed text to show.
Gaudenz
--
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-11-16 12:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 20:08 Hamish D
2010-11-08 11:21 ` Hamish D
2010-11-08 22:32 ` Hamish D
2010-11-11 9:09 ` Gaudenz Steinlin
2010-11-11 17:25 ` Hamish D
2010-11-16 11:42 ` Gaudenz Steinlin [this message]
2010-11-16 14:20 ` Hamish D
2010-11-16 18:36 ` Gaudenz Steinlin
2010-11-16 23:05 ` Hamish D
2010-11-28 22:51 ` Hamish D
2010-11-29 9:41 ` Gaudenz Steinlin
2010-11-30 6:22 ` Tero Tilus
2010-12-01 8:37 ` Gaudenz Steinlin
2010-12-06 23:31 ` Hamish D
2010-12-23 18:43 ` Rich Lane
2011-01-19 3:11 ` Rich Lane
2011-01-30 23:57 ` Hamish D
2011-01-30 23:59 ` Hamish D
2011-01-19 16:12 ` Alvaro Herrera
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=1289907535-sup-3989@meteor.durcheinandertal.local \
--to=gaudenz@soziologie.ch \
--cc=sup-devel@rubyforge.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