From: Leo Liu <sdl.web@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: behaviour change in cl-subseq
Date: Thu, 06 Aug 2015 08:10:29 +0800 [thread overview]
Message-ID: <m1614tff9m.fsf@zeuss-MBP.lan> (raw)
In-Reply-To: 87pp32orsy.fsf@newcastle.ac.uk
On 2015-08-05 20:14 +0800, Phillip Lord wrote:
> (cl-subseq '() 10 10) ;; errors
What did you get when you run it in Common Lisp?
Leo
next prev parent reply other threads:[~2015-08-06 0:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 12:14 behaviour change in cl-subseq Phillip Lord
2015-08-06 0:10 ` Leo Liu [this message]
2015-08-06 6:11 ` Tassilo Horn
2015-08-06 9:34 ` Phillip Lord
2015-08-06 9:48 ` Leo Liu
2015-08-07 14:00 ` Phillip Lord
2015-08-07 14:26 ` Nicolas Petton
2015-08-07 15:51 ` Phillip Lord
2015-08-07 16:08 ` Nicolas Petton
2015-08-07 21:23 ` Phillip Lord
2015-08-08 19:56 ` Nicolas Petton
2015-08-20 20:50 ` Phillip Lord
2015-08-21 0:02 ` Artur Malabarba
2015-08-06 8:08 ` Nicolas Petton
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1614tff9m.fsf@zeuss-MBP.lan \
--to=sdl.web@gmail.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).