From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Problem could be encode-coding-region
Date: Thu, 30 Nov 2006 20:11:39 +0900 [thread overview]
Message-ID: <b4mlklt2npw.fsf@jpl.org> (raw)
In-Reply-To: <87u00hnsk9.fsf@mat.ucm.es>
>>>>> In <87u00hnsk9.fsf@mat.ucm.es> Uwe Brauer wrote:
Katsumi> Yes, using `pgg-sign-region' and `pgg-encrypt-region' causes
Katsumi> such an error. But do you really need to use them? If so,
> I thought I have to use them, what other signing and encryption
> function exists for gnupgp??? My setting is
> (setq pgg-cache-passphrase t
> pgg-default-scheme 'gpg
> pgg-default-user-id "oub"
> pgg-passphrase-cache-expiry 1800
> pgg-scheme 'gpg)
Another way is to use the APEL XEmacs package[1] which provides
some dummy Mule functions except `buffer-file-coding-system'. I
verified I can use `pgg-sign-region' and `pgg-encrypt-region' in
XEmacs 21.4.19 (with no mule no file-coding) by putting the
following snippet in the XEmacs init file.
--8<---------------cut here---------------start------------->8---
(require 'poem)
(defvar buffer-file-coding-system nil)
--8<---------------cut here---------------end--------------->8---
[1] ftp://ftp.xemacs.org/xemacs/packages/apel-1.32-pkg.tar.gz
next prev parent reply other threads:[~2006-11-30 11:11 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 [this message]
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=b4mlklt2npw.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).