From: Daiki Ueno <ueno@unixuser.org>
Subject: default-enable-multibyte-characters in pgg-gpg
Date: Wed, 29 Mar 2006 14:51:53 +0900 [thread overview]
Message-ID: <cda79820-6582-46f3-80d0-0ecd06fe9d1b@well-done.deisui.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
Hello,
Setting default-enable-multibyte-characters in pgg-gpg-start-process
makes GnuPG messages unreadable under multibyte locales.
I found the article which introduced this change:
http://article.gmane.org/gmane.emacs.gnus.general/50457
I think this case is rare, and doubt that this really fixed the problem.
Could anyone who can use a German keyboard check the attached patch?
[-- Attachment #2: pgg-gpg.el.diff --]
[-- Type: application/octet-stream, Size: 548 bytes --]
Index: lisp/pgg-gpg.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/pgg-gpg.el,v
retrieving revision 7.16
diff -u -r7.16 pgg-gpg.el
--- lisp/pgg-gpg.el 27 Mar 2006 09:34:18 -0000 7.16
+++ lisp/pgg-gpg.el 29 Mar 2006 05:51:07 -0000
@@ -82,7 +82,6 @@
(coding-system-for-write 'binary)
(process-connection-type nil)
(orig-mode (default-file-modes))
- default-enable-multibyte-characters
(buffer (generate-new-buffer " *pgg-gpg*"))
process)
(with-current-buffer buffer
[-- Attachment #3: Type: text/plain, Size: 25 bytes --]
Regards,
--
Daiki Ueno
next reply other threads:[~2006-03-29 5:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 5:51 Daiki Ueno [this message]
2006-03-29 11:24 ` Reiner Steib
2006-03-29 11:59 ` Daiki Ueno
2006-03-29 13:31 ` Reiner Steib
2006-03-29 15:16 ` Simon Josefsson
2006-03-29 19:59 ` PGG: byte length problem in pass-phrase (was: default-enable-multibyte-characters in pgg-gpg) Reiner Steib
2006-03-30 0:41 ` PGG: byte length problem in pass-phrase Daiki Ueno
2006-03-30 8:59 ` Simon Josefsson
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=cda79820-6582-46f3-80d0-0ecd06fe9d1b@well-done.deisui.org \
--to=ueno@unixuser.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).