Gnus development mailing list
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@work.lexort.com>
To: Charles Philip Chan <cpchan@sympatico.ca>
Cc: ding@gnus.org
Subject: Re: New imap Implementation and Keepalive
Date: Sat, 25 Sep 2010 18:08:48 -0400	[thread overview]
Message-ID: <smuhbhdearz.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <87k4m94phq.fsf@MagnumOpus.khem> (Charles Philip Chan's message of "Sat, 25 Sep 2010 15:01:05 -0400")

[-- Attachment #1: Type: text/plain, Size: 947 bytes --]


Charles Philip Chan <cpchan@sympatico.ca> writes:

> CHENG Gao <chenggao@cyberhut.org> writes:
>
>> I use also gpg2+gpg-agent+pinentry though under MacOSX. And I use
>> leafnode like you. I dont have any problem so I guess problem may lie
>> in your settings.
>
> So the pinentry dialog doesn't pop up for you after the passphrase
> cache expires? 

I use gpg with pinentry-gtk2.  When trying to sign or decrypt, if the
passphrase is not cached, the dialog pops up, and then when it's done,
the operation proceeds.  Then future operations succeed until the cache
expires.

It's true that when the window pops up interrupting emacs doesn't make
the window go away.  What happens is that emacs ran gpg which sent a
query to the gpg-agent process, which popped up the window.  So you
could argue that gpg should withdraw the request when killed, and that
this is a gpg bug.  But I don't think there's anything wrong with gnus.

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

  reply	other threads:[~2010-09-25 22:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23  2:42 Charles Philip Chan
2010-09-23 16:09 ` Lars Magne Ingebrigtsen
2010-09-23 19:29   ` Frank Schmitt
2010-09-23 19:45     ` Lars Magne Ingebrigtsen
2010-09-23 20:23       ` Frank Schmitt
2010-09-23 20:28         ` Lars Magne Ingebrigtsen
2010-09-24  1:01 ` Uday S Reddy
2010-09-24 12:34   ` Frank Schmitt
2010-09-24 16:34     ` Lars Magne Ingebrigtsen
2010-09-25  5:21       ` Charles Philip Chan
2010-09-25  6:14         ` Charles Philip Chan
2010-09-25 13:43           ` Lars Magne Ingebrigtsen
2010-09-25 14:07             ` Charles Philip Chan
2010-09-25 14:16               ` Lars Magne Ingebrigtsen
2010-09-25 16:01                 ` Charles Philip Chan
2010-09-25 16:14                   ` Lars Magne Ingebrigtsen
2010-09-25 17:23                     ` Dave Goldberg
2010-09-25 18:08                       ` Charles Philip Chan
2010-09-25 18:22                         ` David Engster
2010-09-25 17:53                     ` Charles Philip Chan
2010-09-25 17:35               ` CHENG Gao
2010-09-25 19:01                 ` Charles Philip Chan
2010-09-25 22:08                   ` Greg Troxel [this message]
2010-09-26  1:59                     ` Charles Philip Chan
2010-09-25 12:52     ` Uday S Reddy
2010-09-24 13:00   ` Charles Philip Chan
2010-09-25 12:59     ` Uday S Reddy
2010-09-25 13:08       ` Rupert Swarbrick
2010-09-25 15:21       ` Ted Zlatanov
2010-09-25 23:03         ` Uday S Reddy
2010-09-25 15:48       ` Austin F. Frank

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=smuhbhdearz.fsf@linuxpal.mit.edu \
    --to=gdt@work.lexort.com \
    --cc=cpchan@sympatico.ca \
    --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).