From: Gary <gary@boltav.plus.com>
To: Glenn Morris <rgm@gnu.org>, 21589@debbugs.gnu.org
Subject: bug#21589: 24.5; contradiction in info
Date: Wed, 30 Sep 2015 14:07:53 +0100 [thread overview]
Message-ID: <560BDEA9.7060908@boltav.plus.com> (raw)
In-Reply-To: <kya8s494eg.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
Hi Glenn
thanks for your quick reply. I see what you mean, the append is further
down and I was looking at the code following this comment where it says
'append' (line 3 below) and then uses cons (line 6). On the other hand
being a new user, I NEED to read the manual whereas I'm guessing you
don't. :)
cheers
Gary
(cond
;; check to see whether filename ends in `.el'
;; and if so, append its name to a list.
((equal ".el" (substring (car (car current-directory-list))
-3))
(setq el-files-list
(cons (car (car current-directory-list))
el-files-list)))
;; check whether filename is that of a directory
((eq t (car (cdr (car current-directory-list))))
;; decide whether to skip or recurse
On 30/09/15 00:44, Glenn Morris wrote:
> Gary wrote:
>
>> The info section Recursive Pattern: _accumulate_ states:
>>
>> 'This is very like the 'every' pattern using 'cons', except that
>> 'cons' is not used, but some other combiner.'
>>
>> The example link 'Making a List of Files' uses cons to accumulate a list
>> of files.
> The recursive function call (which is what the section "Recursive
> Patterns" is about) in files-in-below-directory uses "append", not cons.
> cons happens to be used elsewhere in the function. It says right before
> the files-in-below-directory definition that it uses "append".
> So personally speaking I don't find it confusing.
>
[-- Attachment #2: Type: text/html, Size: 2121 bytes --]
next prev parent reply other threads:[~2015-09-30 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 21:55 bug#21589: 24.5; contradiction in info Gary
2015-09-29 23:44 ` Glenn Morris
2015-09-30 13:07 ` Gary [this message]
2016-06-27 3:53 ` Noam Postavsky
2016-07-29 0:10 ` npostavs
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=560BDEA9.7060908@boltav.plus.com \
--to=gary@boltav.plus.com \
--cc=21589@debbugs.gnu.org \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.