From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: XEmacs builds failing - gnus-spec.el
Date: Tue, 21 May 2013 08:55:48 +0900 [thread overview]
Message-ID: <b4mli79ury3.fsf@jpl.org> (raw)
In-Reply-To: <874ndxppzz.fsf@topper.koldfront.dk>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
Adam Sjøgren wrote:
> Oh, I can - evaluating:
> (message (format "%s" ?\u00AB))
> in both mule and nomule XEmacs 21.4.22 gives me:
> Symbol's value as variable is void: 00AB
Yes, XEmacs 21.4 doesn't support such read sequence.
> I wonder if it would work to simply replace ?\u00AB with 171.
?\« is ok for XEmacs 21.4 if it loads the Mule-UCS package that
provides the utf-8 coding system. To use it, do:
(require 'un-define)
But as for loading gnus-spec.el, there's another problem for
XEmacs 21.4; the coding cookie, put in the `Local Variables'
section at the end of the file, won't be effective. So,
gnus-spec.el will not necessarily be loaded as a utf-8 file.
AFAIK, the only effective coding cookie is the one put at
the beginning of a file.
A patch that involves those consideration is below.
BTW, isn't it possible for Gnus to drop the XEmacs 21.4 support?
[-- Attachment #2: Type: text/x-patch, Size: 1110 bytes --]
--- dgnushack.el~ 2013-01-06 22:08:11 +0000
+++ dgnushack.el 2013-05-20 23:53:55 +0000
@@ -24,6 +24,13 @@
;;; Code:
+(if (and (featurep 'xemacs)
+ (fboundp 'find-coding-system)
+ (not (find-coding-system 'utf-8)))
+ (condition-case nil
+ (require 'un-define)
+ (error nil)))
+
(defvar dgnushack-default-load-path (copy-sequence load-path))
(defalias 'facep 'ignore)
--- gnus-spec.el~ 2013-05-20 22:12:26 +0000
+++ gnus-spec.el 2013-05-20 23:53:57 +0000
@@ -1,4 +1,4 @@
-;;; gnus-spec.el --- format spec functions for Gnus
+;;; gnus-spec.el --- format spec functions for Gnus -*- coding: utf-8 -*-
;; Copyright (C) 1996-2013 Free Software Foundation, Inc.
@@ -441,7 +441,7 @@
(delim (aref (match-string 2) 0)))
(if (or (= delim ?\()
(= delim ?\{)
- (= delim ?\u00AB)) ; «
+ (= delim ?\«))
(replace-match (concat "\"("
(cond ((= delim ?\() "mouse")
((= delim ?\{) "face")
@@ -732,8 +732,4 @@
(provide 'gnus-spec)
-;; Local Variables:
-;; coding: utf-8
-;; End:
-
;;; gnus-spec.el ends here
next prev parent reply other threads:[~2013-05-20 23:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 19:23 Adam Sjøgren
2013-05-19 21:45 ` Mike Kupfer
2013-05-19 21:58 ` Adam Sjøgren
2013-05-19 22:13 ` Adam Sjøgren
2013-05-19 23:30 ` Adam Sjøgren
2013-05-20 7:39 ` David Engster
2013-05-20 16:01 ` Adam Sjøgren
2013-05-20 16:36 ` Adam Sjøgren
2013-05-20 23:55 ` Katsumi Yamaoka [this message]
2013-05-21 21:01 ` Adam Sjøgren
2013-05-21 23:39 ` Katsumi Yamaoka
2013-05-22 2:58 ` Mike Kupfer
2013-05-22 5:45 ` Katsumi Yamaoka
2013-05-28 0:22 ` Mike Kupfer
2013-05-31 12:07 ` Mats Lidell
2013-05-22 20:18 ` Adam Sjøgren
2013-05-22 20:28 ` Adam Sjøgren
2013-05-22 20:36 ` David Engster
2013-05-28 0:43 ` Mike Kupfer
2013-06-01 22:04 ` XEmacs hash table representation (was XEmacs builds failing - gnus-spec.el) Mike Kupfer
2013-06-02 8:59 ` David Engster
2013-06-02 16:22 ` Mike Kupfer
2013-06-06 14:46 ` Ted Zlatanov
2013-06-06 16:06 ` Mike Kupfer
2013-05-22 3:02 ` XEmacs builds failing - gnus-spec.el Mike Kupfer
2013-05-22 20:25 ` David Engster
2013-05-28 0:25 ` Mike Kupfer
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=b4mli79ury3.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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).