From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Problem could be encode-coding-region
Date: Thu, 30 Nov 2006 08:12:28 +0900 [thread overview]
Message-ID: <b4mhcwhvodf.fsf@jpl.org> (raw)
In-Reply-To: <87ejrm8c2j.fsf_-_@mat.ucm.es>
>>>>> In <87ejrm8c2j.fsf_-_@mat.ucm.es> Uwe Brauer wrote:
> I just run pgg-sign-region and pgg-encrypt-región
> for the first command I obtain (void-function encode-coding-region)
> for the second it seems a similar error. I attach both backtraces.
> I am on XEmacs 21.4.19 no mule. So I tried no mule and then the region
> got deleted. So I presume something with my gnupg setting is wrong but
> I am not sure what.
I tested signing and encrypting a messege using `C-c C-m s p'
and `C-c C-m c p' in XEmacs 21.4.19 with no Mule. No Problem.
Yes, using `pgg-sign-region' and `pgg-encrypt-region' causes
such an error. But do you really need to use them? If so,
please contact the PGG author. I don't modify PGG files because
the author will probably not want me to do it.
OTOH, I found similar things by performing
egrep '\((de|en)code-coding-' *.el
in files other than PGG. So, I will fix only them later.
Regards,
next prev parent reply other threads:[~2006-11-29 23:12 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 ` Katsumi Yamaoka [this message]
2006-11-30 10:21 ` Problem could be encode-coding-region 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=b4mhcwhvodf.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).