unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daiki Ueno <ueno@unixuser.org>
To: Torsten Bronger <bronger@physik.rwth-aachen.de>
Cc: emacs-pretest-bug@gnu.org, 3953@emacsbugs.donarmstrong.com
Subject: bug#3953: 23.0.94; GPG interaction fails
Date: Tue, 28 Jul 2009 19:34:27 +0900	[thread overview]
Message-ID: <5fb842ac-b803-4894-8c58-f514f1967a2a@broken.deisui.org> (raw)
In-Reply-To: <20090727194515.F1958E42E9@wilson.homeunix.com> (Torsten Bronger's message of "Mon, 27 Jul 2009 21:45:15 +0200 (CEST)")

reopen 2412
merge 2412 3953
thanks

>>>>> In <20090727194515.F1958E42E9@wilson.homeunix.com> 
>>>>>	Torsten Bronger <bronger@physik.rwth-aachen.de> wrote:
> >>> -    (accept-process-output (epg-context-process context) 1)))
> >>> +    (accept-process-output (epg-context-process context) 1))
> >>> +  (sleep-for 0.1))
> >>
> >> That seems to do the trick.  At least, I had no problem in ~15 attempts
> >> to preview/send signed messages, whereas without your patch the "Sign
> >> failed" error would happen about every second time.
> >
> > Thanks for testing.  I've checked in the patch.

> I experience the same problem but the above patch doesn't really
> help me.  Without the sleeping time, I get failures with signature
> checking of incoming emails almost always; with the sleeping time,
> it works at least in 20% of the cases.  I increased the time to even
> 10 seconds but the success rate didn't increase further.  The
> behaviour remains probabilistic.

Thanks for further testing.  Well, in that case an essential part of
process-filter might not be executed in 20% of the cases.

Does replacing (sleep-for 0.1) with:

(epg--process-filter (epg-context-process context) "")

change the situation?

Regards,
-- 
Daiki Ueno





  reply	other threads:[~2009-07-28 10:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <878whrarbh.fsf@cyd.mit.edu>
2009-07-27 19:45 ` bug#3953: 23.0.94; GPG interaction fails Torsten Bronger
2009-07-28 10:34   ` Daiki Ueno [this message]
2009-07-28 21:25     ` Torsten Bronger
2009-07-28 22:54       ` Daiki Ueno
2009-07-29 19:26         ` Torsten Bronger
2009-07-29 23:59           ` Daiki Ueno
2009-07-30  4:57             ` Torsten Bronger
2009-07-30  5:05               ` Daiki Ueno
2009-07-30  5:43                 ` Torsten Bronger
2009-08-16 11:30             ` Torsten Bronger
     [not found]   ` <handler.3953.C.124996607716130.notifdonectrl.5@emacsbugs.donarmstrong.com>
2009-08-12 13:30     ` bug#3953: acknowledged by developer (process bugs) Torsten Bronger
2009-08-26 11:51       ` Sven Joachim
2009-08-26 12:00         ` Processed: Re: bug#3953 " Emacs bug Tracking System
2009-08-11  4:55 ` Processed: process bugs Emacs bug Tracking System
2009-08-03  9:52 bug#3953: 23.0.94; GPG interaction fails Ashish SHUKLA

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5fb842ac-b803-4894-8c58-f514f1967a2a@broken.deisui.org \
    --to=ueno@unixuser.org \
    --cc=3953@emacsbugs.donarmstrong.com \
    --cc=bronger@physik.rwth-aachen.de \
    --cc=emacs-pretest-bug@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).