From: Steven L Baur <steve@xemacs.org>
Subject: Re: gnus-change-server problems?
Date: 02 Jun 1997 03:46:53 -0700 [thread overview]
Message-ID: <m27mgdmgde.fsf@altair.xemacs.org> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "31 May 1997 13:40:06 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Chris Halverson <cdh@CompleteIS.com> writes:
>> Signaling: (wrong-type-argument number-or-marker-p nil)
>> <(nil nil)
>> sort((nil) <)
> Hm.
> (sort '(nil) '<)
> => (nil)
> (sort nil '<)
> => nil
> This is with Emacs 19.34. Is this illegal under XEmacs?
Not as far as I can tell (tested against 19.15 and 20.3beta). If it
is being considered illegal, it's an XEmacs bug.
--
steve@calag.com baur
Unsolicited commercial e-mail will be billed at $250/message.
next prev parent reply other threads:[~1997-06-02 10:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-30 19:09 Chris Halverson
1997-05-31 11:40 ` Lars Magne Ingebrigtsen
1997-06-02 10:46 ` Steven L Baur [this message]
1997-06-02 14:47 ` Hrvoje Niksic
1997-06-02 15:07 ` Chris Halverson
1997-06-06 3:26 ` Lars Magne Ingebrigtsen
1997-06-06 14:34 ` Chris Halverson
1997-06-06 17:44 ` Lars Magne Ingebrigtsen
1997-06-06 21:36 ` Steven L Baur
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=m27mgdmgde.fsf@altair.xemacs.org \
--to=steve@xemacs.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).