From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: mml problem for gnupgp
Date: Wed, 29 Nov 2006 14:53:55 +0900 [thread overview]
Message-ID: <b4mac2aiyrw.fsf@jpl.org> (raw)
In-Reply-To: <87r6vn8u48.fsf@mat.ucm.es>
[-- Attachment #1.1: Type: text/plain, Size: 714 bytes --]
>>>>> In <87r6vn8u48.fsf@mat.ucm.es> Uwe Brauer wrote:
> The following puzzles me: I have used successfully mml with gnupg for
> a while. Recently I started again using it.
> However when I try to sign or encrypt a message I receive after I am
> asked for the passwd, the following error message which I attach below.
> I test gpg on the command line and there seems no problem
> Thanks
> Uwe Brauer
> Debugger entered--Lisp error: (search-failed "
> ")
> search-forward("\n\n")
> pgg-decode-armor-region(1 1)
It seems that generating a detached sign failed. (1 1) means
there is no content in the buffer. I'm sorry I don't know what
causes it since I have no problem with the latest Gnus and GnuPG.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 191 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
http://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2006-11-29 5:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 15:32 Uwe Brauer
2006-11-29 5:53 ` Katsumi Yamaoka [this message]
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
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=b4mac2aiyrw.fsf@jpl.org \
--to=yamaoka@jpl.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).