From: deskpot@despammed.com (Vasily Korytov)
Subject: Re: Bug in rfc2047.el
Date: Sun, 04 May 2003 04:08:49 +0400 [thread overview]
Message-ID: <878ytny3n2.fsf@unix.home> (raw)
In-Reply-To: <m3r87fmxmp.fsf@hamster.pflaesterer.de>
[-- Attachment #1: Type: text/plain, Size: 246 bytes --]
On Sun, 04 May 2003 01:28:42 +0200, Karl PflДsterer wrote:
> For XEmacs the parameter must be `'syntax' not `'syntax-table'.
This isn't the only error. I'm not sure, if I broke smth, but here is
the patch, that leads gnus here to byte-compile.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: rfc2047.el.patch --]
[-- Type: text/x-patch, Size: 866 bytes --]
Index: rfc2047.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/rfc2047.el,v
retrieving revision 6.45
diff -u -r6.45 rfc2047.el
--- rfc2047.el 3 May 2003 14:20:49 -0000 6.45
+++ rfc2047.el 4 May 2003 00:06:35 -0000
@@ -246,11 +246,7 @@
;; skip to the end of regions appropriately. Nb. ietf-drums does
;; things differently.
(defconst rfc2047-syntax-table
- ;; This is what we should do, but XEmacs doesn't support the optional
- ;; arg of `make-syntax-table':
-;; (let ((table (make-char-table 'syntax-table '(2))))
- (let ((table (make-char-table 'syntax-table)))
- (map-char-table (lambda (k v) (aset table k '(2))) table)
+ (let ((table (make-syntax-table '(2))))
(modify-syntax-entry ?\\ "\\" table)
(modify-syntax-entry ?\" "\"" table)
(modify-syntax-entry ?\( "." table)
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
--
I accept RFC3156 and RFC2440-compatible encrypted mail.
PGP key fingerprint: 123A 7CCE 6E26 6233 0D87 E01A A0F8 3524 FCD8 1841
next prev parent reply other threads:[~2003-05-04 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-03 23:28 Karl Pflästerer
2003-05-04 0:08 ` Vasily Korytov [this message]
2003-05-04 2:46 ` Katsumi Yamaoka
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=878ytny3n2.fsf@unix.home \
--to=deskpot@despammed.com \
/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).