From: Philip Kaludercic <philipk@posteo.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
"Stefan Monnier" <monnier@iro.umontreal.ca>,
"Protesilaos Stavrou" <info@protesilaos.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [External] : Re: [elpa] main 2ec80977e1: * elpa-packages (dired-preview): New package
Date: Fri, 14 Jul 2023 19:29:51 +0000 [thread overview]
Message-ID: <87r0pap9zk.fsf@posteo.net> (raw)
In-Reply-To: <SJ0PR10MB54880229DE02D1ACCBEBEB06F334A@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Fri, 14 Jul 2023 14:18:34 +0000")
Drew Adams <drew.adams@oracle.com> writes:
> While on the subject of `dolist' versus `mapc',
> I'd add that code with `dolist' looks more like
> usual imperative programming constructs (e.g.,
> it looks like C or Fortran), and `mapc' looks,
> perhaps misleadingly, more like functional
> programming mapping over streams.
>
> IOW, IMO there's no great use case for `mapc'
> on a list, but I suppose maybe someone might
> find it clearer than `dolist' when used in a
> context where there's already some other
> mapping involved.
I rgrep'ed my own code and found this block I still find convenient,
because I don't have to come up with a name (even though `var' would
probably be a sufficiently good fit here, I guess):
--8<---------------cut here---------------start------------->8---
(mapc #'kill-local-variable
'(enable-local-variables
header-line-format
buffer-read-only))
--8<---------------cut here---------------end--------------->8---
next prev parent reply other threads:[~2023-07-14 19:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168884609732.27984.6450580686777461843@vcs2.savannah.gnu.org>
[not found] ` <20230708195457.95F1AC11DD8@vcs2.savannah.gnu.org>
2023-07-08 21:47 ` [elpa] main 2ec80977e1: * elpa-packages (dired-preview): New package Stefan Monnier
2023-07-09 2:29 ` Protesilaos Stavrou
2023-07-10 18:29 ` Philip Kaludercic
2023-07-10 20:20 ` Protesilaos Stavrou
2023-07-10 21:13 ` Stefan Monnier
2023-07-11 7:47 ` Philip Kaludercic
2023-07-11 13:33 ` Stefan Monnier
2023-07-11 16:58 ` Philip Kaludercic
2023-07-11 18:45 ` Stefan Monnier
2023-07-13 18:40 ` Protesilaos Stavrou
2023-07-13 20:29 ` Philip Kaludercic
2023-07-13 21:36 ` Stefan Monnier
2023-07-14 8:13 ` Mattias Engdegård
2023-07-14 14:18 ` [External] : " Drew Adams
2023-07-14 19:29 ` Philip Kaludercic [this message]
2023-07-18 19:06 ` Stefan Monnier
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=87r0pap9zk.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=info@protesilaos.com \
--cc=mattiase@acm.org \
--cc=monnier@iro.umontreal.ca \
/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.