Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: [PATCH] Fix gnus-message-citation-mode for (S)XEmacs
Date: Mon, 01 Jan 2007 16:26:16 +0900	[thread overview]
Message-ID: <b4m8xgnp5ra.fsf@jpl.org> (raw)
In-Reply-To: <v9r6ugwadx.fsf@marauder.physik.uni-ulm.de>

>>>>> In <v9r6ugwadx.fsf@marauder.physik.uni-ulm.de>
>>>>>	Reiner Steib <reinersteib+gmane@imap.cc> wrote:

> On Sun, Dec 31 2006, Steve Youngs wrote:

[...]

>>  (eval-when-compile (require 'cl))
>> +(eval-when-compile
>> +  (when (featurep 'xemacs)
>> +    (require 'easy-mmode))) ; for `define-minor-mode'

> Hm, I'm surprised that (S)XEmacs' byte-compiler doesn't complain in
> the first place.

I found the cause that building of Gnus with XEmacs 21.4 failed
as follows:

Compiling gnus/lisp/gnus-cite.el...
While compiling toplevel forms in file gnus/lisp/gnus-cite.el:
  !! Wrong type argument ((char-or-string-p nil))

In xemacs-base/easy-mmode.el, the `replace-regexp-in-string'
function is defined if it is not bound, and the
`define-minor-mode' macro uses it when compiling.  However,
lpath.el binds it to `ignore' before easy-mmode.el is loaded
(see dgnushack.el).  So, `define-minor-mode' uses the version of
`replace-regexp-in-string' that always returns nil.

I've removed `replace-regexp-in-string' from lpath.el in the
trunk temporarily.  However, I think the best way is to make
easy-mmode.el use `replace-in-string' instead of
`replace-regexp-in-string'.  That XEmacs easily provides the
Emacs functions causes confusion.

I've also done some minor fixes in the v5-10 branch and the
trunk.  They are mainly for only making the byte compiler
silent, don't influence the behavior of Gnus.

Regards,



  reply	other threads:[~2007-01-01  7:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-31  7:18 Steve Youngs
2006-12-31 11:52 ` Reiner Steib
2007-01-01  7:26   ` Katsumi Yamaoka [this message]
2007-02-07  9:25     ` Katsumi Yamaoka
2007-02-07 15:33       ` Dave Goldberg
2007-02-08  4:42         ` Katsumi Yamaoka
2007-02-08 17:48           ` Dave Goldberg
2007-02-08 23:29             ` Katsumi Yamaoka
2007-02-13 12:46               ` Katsumi Yamaoka
2007-02-13 19:49                 ` Dave Goldberg
2007-02-14  0:29                   ` Katsumi Yamaoka
2007-02-28 21:14                     ` Dave Goldberg
2007-02-28 22:32                       ` Katsumi Yamaoka
2007-03-01 16:29                         ` Dave Goldberg
2007-03-02 15:28                           ` Dave Goldberg
2007-02-09 23:48       ` Steve Youngs

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=b4m8xgnp5ra.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).