From: sigurd@12move.de (Karl Pflästerer)
Subject: Bug in rfc2047.el
Date: Sun, 04 May 2003 01:28:42 +0200 [thread overview]
Message-ID: <m3r87fmxmp.fsf@hamster.pflaesterer.de> (raw)
Hi,
the current cvs heaad version doesn't compile with XEmacs. This is
because of an bug in rfc2047.el.
Line 252; cvs version 6.45
(let ((table (make-char-table 'syntax-table)))
For XEmacs the parameter must be `'syntax' not `'syntax-table'.
,----[ C-h f make-char-table RET ]
| `make-char-table' is a built-in function
| (make-char-table TYPE)
|[...]
| Each char table type is used for a different purpose and allows different
| sorts of values. The different char table types are
|
| `category'
| Used for category tables, which specify the regexp categories
| that a character is in. The valid values are nil or a
| bit vector of 95 elements. Higher-level Lisp functions are
| provided for working with category tables. Currently categories
| and category tables only exist when Mule support is present.
| `char'
| A generalized char table, for mapping from one character to
| another. Used for case tables, syntax matching tables,
| `keyboard-translate-table', etc. The valid values are characters.
| `generic'
| An even more generalized char table, for mapping from a
| character to anything.
| `display'
| Used for display tables, which specify how a particular character
| is to appear when displayed. #### Not yet implemented.
| `syntax'
| Used for syntax tables, which specify the syntax of a particular
| character. Higher-level Lisp functions are provided for
| working with syntax tables. The valid values are integers.
`----
I don't post a patch as I don't know the right syntax for Emacs.
bye
KP
--
One, two! One, two! And through and through
The vorpal blade went snicker-snack!
He left it dead, and with its head
He went galumphing back. "Lewis Carroll" "Jabberwocky"
next reply other threads:[~2003-05-03 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-03 23:28 Karl Pflästerer [this message]
2003-05-04 0:08 ` Vasily Korytov
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=m3r87fmxmp.fsf@hamster.pflaesterer.de \
--to=sigurd@12move.de \
/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).