From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: request for a new function, say, `sequence'
Date: Wed, 26 Mar 2003 10:44:04 -0500 [thread overview]
Message-ID: <200303261544.h2QFi4i4022332@rum.cs.yale.edu> (raw)
In-Reply-To: 200303252311.IAA08003@etlken.m17n.org
> Yes, I know. But the main reason for my proposal is for
> readability. Currently, the above function is used mainly
> for defining a data in defvar, so the speed is not that
> important. On the other hand, XXX-util.el (especially the
> data definition parts) must be read and modified by native
> XXX users who may not be familiar with lisp. So, it's very
> important to provide easy-to-understand data definition
> parts.
Makes sense.
> As far as I see the current usage, a function returning a
> list is enough. So, I don't insist on having TYPE argument.
Good.
> > Anyway, blue is the color for my bykeshed, what is yours ?
> What is "bykeshed"? My dictionary doesn't have that word.
Sorry, typo. See http://www.unixguide.net/freebsd/faq/16.19.shtml.
So, please go ahead and install that function, whatever its name is
going to be. I still hope we'll get a chance to change dotimes since
it is frequent to need something like dotimes but that starts at
something else than 0.
Stefan
next prev parent reply other threads:[~2003-03-26 15:44 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 3:02 request for a new function, say, `sequence' Kenichi Handa
2003-03-24 15:41 ` Stefan Monnier
2003-03-25 0:15 ` Kenichi Handa
2003-03-25 0:50 ` Kenichi Handa
2003-03-25 0:57 ` Stefan Monnier
2003-03-25 1:25 ` Kenichi Handa
2003-03-25 1:47 ` Luc Teirlinck
2003-03-25 1:51 ` Luc Teirlinck
2003-03-25 1:59 ` Kenichi Handa
2003-03-25 2:29 ` Luc Teirlinck
2003-03-25 1:57 ` Satyaki Das
2003-03-25 2:08 ` Kenichi Handa
2003-03-25 2:41 ` Satyaki Das
2003-03-25 4:46 ` Kenichi Handa
2003-03-25 5:05 ` Satyaki Das
2003-03-25 5:40 ` Kenichi Handa
2003-03-25 20:10 ` Satyaki Das
2003-03-26 0:18 ` Kenichi Handa
2003-03-26 1:44 ` Satyaki Das
2003-03-26 2:38 ` Luc Teirlinck
2003-03-26 7:31 ` Edward O'Connor
2003-03-26 8:48 ` Thien-Thi Nguyen
2003-03-26 12:18 ` Kenichi Handa
2003-03-27 3:30 ` Richard Stallman
2003-04-03 2:54 ` Kenichi Handa
2003-04-03 3:44 ` Miles Bader
2003-04-03 22:52 ` Richard Stallman
2003-04-03 10:41 ` Thien-Thi Nguyen
2003-04-04 2:11 ` Vinicius Jose Latorre
2003-04-04 22:23 ` Richard Stallman
2003-04-05 2:10 ` Vinicius Jose Latorre
2003-04-06 2:00 ` Richard Stallman
2003-04-08 8:10 ` Kenichi Handa
2003-04-03 22:52 ` Richard Stallman
2003-03-25 15:27 ` Stefan Monnier
2003-03-25 23:11 ` Kenichi Handa
2003-03-26 0:11 ` Miles Bader
2003-03-26 0:40 ` Luc Teirlinck
2003-03-26 1:34 ` Miles Bader
2003-03-26 0:54 ` Kenichi Handa
2003-03-26 1:29 ` Miles Bader
2003-03-26 15:44 ` Stefan Monnier [this message]
2003-03-27 0:09 ` Luc Teirlinck
2003-03-27 15:20 ` Stefan Monnier
2003-03-27 15:53 ` Luc Teirlinck
2003-03-27 16:06 ` Stefan Monnier
2003-03-27 17:03 ` Luc Teirlinck
2003-03-27 17:08 ` Stefan Monnier
2003-03-26 2:41 ` Richard Stallman
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=200303261544.h2QFi4i4022332@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
/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).