From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Nicolas Petton <nicolas@petton.fr>
Cc: Bozhidar Batsov <bozhidar@batsov.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: New macro `seq-let' in seq.el
Date: Tue, 05 May 2015 23:08:18 -0400 [thread overview]
Message-ID: <jwvegmubdz2.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87egmulr1k.fsf@petton.fr> (Nicolas Petton's message of "Tue, 05 May 2015 22:15:19 +0200")
> and I was wondering if there was a reason for the function to be
> so long.
It just grew.
Stefan
next prev parent reply other threads:[~2015-05-06 3:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 17:37 New macro `seq-let' in seq.el Nicolas Petton
2015-05-05 16:25 ` Bozhidar Batsov
2015-05-05 18:36 ` Nicolas Petton
2015-05-05 19:56 ` Stefan Monnier
2015-05-05 20:15 ` Nicolas Petton
2015-05-06 3:08 ` Stefan Monnier [this message]
2015-05-06 3:46 ` 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=jwvegmubdz2.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=bozhidar@batsov.com \
--cc=emacs-devel@gnu.org \
--cc=nicolas@petton.fr \
/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).