From: Sebastian Lipp <bacuh@riseup.net>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] gpg-options.rb: how to set always_trust
Date: Sun, 23 Jan 2011 23:09:01 +0100 [thread overview]
Message-ID: <1295820417-sup-1526@fly> (raw)
In-Reply-To: <AANLkTimJZiRE31R5KJBdqZv5L17qhKeLjbO4fWM5LfD2@mail.gmail.com>
Excerpts from Hamish D's message of So Jan 23 11:47:32 +0100 2011:
> > I've just 'git pull'ed so my always_trust setting for GnuPG isn't
> > working any more. I tried to set it by just putting
> > {:always_trust => true}
> > into gpg-options.rb but it doesn't work.
>
> This may be slightly obscure,
I expected it would, but as I said I have no clue about ruby. ;)
> if operation == "encrypt"
> options.merge({:always_trust => true})
> end
> options
That is exactly what I was looking for. Thanks.
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?
--
basti
The Web should be like a white sheet of paper: ready to be written on,
with no control over what is written.
-- Tim Berners-Lee
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-01-23 23:34 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 [this message]
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
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=1295820417-sup-1526@fly \
--to=bacuh@riseup.net \
--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