From: mskala@ansuz.sooke.bc.ca
To: xconq7@sources.redhat.com
Subject: Re: (remove) doesn't work
Date: Tue, 18 May 2004 22:26:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0405181825390.5070-100000@diamond.ansuz.sooke.bc.ca> (raw)
In-Reply-To: <Pine.LNX.4.21.0405181803440.5070-200000@diamond.ansuz.sooke.bc.ca>
On Tue, 18 May 2004 mskala@ansuz.sooke.bc.ca wrote:
> As far as I can tell, the (remove) form simply returns its second argument
> instead of doing its job. Test case attached - this will fail regardless
Further to that: it seems it works if the first argument (the thing being
removed) is an atom. You can do 10-1=9, but not 10-3=7. Both my test
case and apparently tailhook.g depend on the documented behaviour of
removing a multi-element list from another multi-element list.
--
Matthew Skala
mskala@ansuz.sooke.bc.ca Embrace and defend.
http://ansuz.sooke.bc.ca/
next prev parent reply other threads:[~2004-05-18 22:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 22:12 mskala
2004-05-18 22:26 ` mskala [this message]
2004-05-19 0:30 ` Eric McDonald
2004-05-19 12:24 ` mskala
2004-05-19 15:44 ` Jim Kingdon
2004-05-19 21:10 ` mskala
2004-06-08 3:10 ` Eric McDonald
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=Pine.LNX.4.21.0405181825390.5070-100000@diamond.ansuz.sooke.bc.ca \
--to=mskala@ansuz.sooke.bc.ca \
--cc=xconq7@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).