Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
Subject: Re: Problem could be encode-coding-region
Date: Fri, 01 Dec 2006 16:25:01 +0100	[thread overview]
Message-ID: <877ixbvdte.fsf@mat.ucm.es> (raw)
In-Reply-To: <b4mbqmowbsa.fsf@jpl.org>




   Katsumi> Hmm, I have no problem in using PGG and XEmacs with no mule no
   Katsumi> file-coding.  Actually I signed this message by it.

   >> Shall I debug (mml-secure-message-sign-pgpmime)?

   Katsumi> No, you should trace `mml2015-pgg-sign' and `pgg-gpg-sign-region'.
   Katsumi> If you'd like to edebug (info "(gnus)Troubleshooting"), perform
   Katsumi> `M-x edebug-defun RET' on those functions, and type `C-c C-m s p'
   Katsumi> and then `C-u C-c C-m P' in the message buffer.

I did this, and the XEmacs gets stuck in pgg-gpg-sign-region


    -    (pgg-gpg-wait-for-status process '("BEGIN_SIGNING"
         "GOOD_PASSPHRASE")))
         is fine but then 

    -  	 (process (pgg-gpg-start-process args))) it gets stuck

`pgg-gpg-use-agent' is nil, I will try now with t.
 
Uwe

  parent reply	other threads:[~2006-12-01 15:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28 15:32 mml problem for gnupgp Uwe Brauer
2006-11-29  5:53 ` Katsumi Yamaoka
2006-11-29 11:07   ` Uwe Brauer
2006-11-29 16:14   ` Problem could be encode-coding-region (was: mml problem for gnupgp) Uwe Brauer
2006-11-29 23:12     ` Problem could be encode-coding-region Katsumi Yamaoka
2006-11-30 10:21       ` Uwe Brauer
2006-11-30 11:11         ` Katsumi Yamaoka
2006-11-30 16:14           ` Uwe Brauer
2006-12-01  3:11             ` Katsumi Yamaoka
2006-12-01  6:01               ` Katsumi Yamaoka
2006-12-01  9:48               ` Rud1ger Sch1erz
2006-12-01 10:27                 ` Katsumi Yamaoka
2006-12-01 12:26               ` Uwe Brauer
2006-12-01 15:25               ` Uwe Brauer [this message]
2006-11-29 16:40   ` vm-pgg works (was: mml problem for gnupgp) Uwe Brauer

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=877ixbvdte.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    /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).