From: Hamish <dmishd@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] gpg-options.rb: how to set always_trust
Date: Sun, 30 Jan 2011 23:04:58 +0000 [thread overview]
Message-ID: <1296428275-sup-8599@whisper> (raw)
In-Reply-To: <1295820417-sup-1526@fly>
Excerpts from Sebastian Lipp's message of Sun Jan 23 22:09:01 +0000 2011:
> Excerpts from Hamish D's message of So Jan 23 11:47:32 +0100 2011:
> > if operation == "encrypt"
> > options.merge({:always_trust => true})
> > end
> > options
>
> That is exactly what I was looking for. Thanks.
I've discovered that it actually needs to be
if operation == "encrypt"
options.merge!({:always_trust => true})
end
options
I've updated the wiki aswell. The difference is using merge! rather than
merge - I discovered this while tracking down your other issue:
> But another problem popped up. Now I can't sign any message. It makes no
> difference if gpg-options.rb is there or not. There is also no difference in
> choosing sign or sign and encrypt. There are no messages about that in
> the log even with debugging turned on. Have I found a bug?
This bug is now fixed in the next branch (and the gpgme branch). Someone
should hopefully merge this into master soon.
http://rubyforge.org/pipermail/sup-devel/2011-January/000965.html
Hamish Downer
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-01-30 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 8:25 Sebastian Lipp
2011-01-23 12:17 ` Michael Stapelberg
[not found] ` <AANLkTimJZiRE31R5KJBdqZv5L17qhKeLjbO4fWM5LfD2@mail.gmail.com>
2011-01-23 22:09 ` Sebastian Lipp
2011-01-24 9:15 ` Shadowfirebird
[not found] ` <AANLkTimrPK4Bt7z+uN5AkShp3uJSw3OdbR2A-R0p4RoA@mail.gmail.com>
[not found] ` <AANLkTimB43mBbe-3EvRxZHCK_n9-Xy0mL1MHRGSO6MTf@mail.gmail.com>
2011-01-24 10:34 ` Hamish D
2011-01-25 14:32 ` Sebastian Lipp
2011-01-30 23:04 ` Hamish [this message]
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=1296428275-sup-8599@whisper \
--to=dmishd@gmail.com \
--cc=sup-talk@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