From: Tino Calancha <tino.calancha@gmail.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: 26338@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>,
Juri Linkov <juri@linkov.net>
Subject: bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer
Date: Wed, 5 Apr 2017 20:58:51 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1704052046350.28514@calancha-pc> (raw)
In-Reply-To: <87pogsmefn.fsf@jane>
On Tue, 4 Apr 2017, Marcin Borkowski wrote:
>> Any interest in something like this?:
>>
>> (defmacro with-collect-matches (regexp &optional group &rest body)
>> "Collect matches for REGEXP and eval BODY for each match.
>> BODY is evaluated with `it' bound to the match.
>> Optional GROUP if non-nil, then is the regexp group to save. Otherwise,
>> save the whole match."
>
> Sorry if this was said already, but why a macro and not a map-like
> function?
No special reason. It's the second idea which came to my mind after
my initial proposal was declined. Maybe because is shorter to do:
(with-collect-matches regexp)
than
(foo-collect-matches regexp nil #'identity)
if you are just interested in the list of matches. Implementing it as
a map function might be also nice. Don't see a big enthusiasm on
the proposal, though :-(
So far people think that it's easy to write a while loop. I wonder
if they think the same about the existence of `dolist': the should
never use it and always write a `while' loop instead. Don't think they
do that anyway.
I will repeat it once more. I find nice, having an operator returning a
list with matches for REGEXP. If such operator, in addition, accepts a
body of code or a function, then i find this operator very nice
and elegant.
Regards,
Tino
next prev parent reply other threads:[~2017-04-05 11:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 12:41 bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer Tino Calancha
2017-04-02 15:57 ` Dmitry Gutov
2017-04-03 3:58 ` Tino Calancha
2017-04-02 22:10 ` Juri Linkov
2017-04-03 4:01 ` Tino Calancha
2017-04-03 6:13 ` Tino Calancha
2017-04-03 23:35 ` Juri Linkov
2017-04-04 1:37 ` Tino Calancha
2017-04-04 2:20 ` Tino Calancha
2017-04-04 14:32 ` Marcin Borkowski
2017-04-05 11:58 ` Tino Calancha [this message]
2017-04-05 13:11 ` npostavs
2017-04-07 10:06 ` Tino Calancha
2017-04-07 14:40 ` Drew Adams
2017-04-08 4:45 ` Tino Calancha
2017-04-08 5:49 ` Drew Adams
2017-04-08 15:29 ` Tino Calancha
2017-04-08 15:42 ` Drew Adams
2017-04-08 11:46 ` Philipp Stephani
2017-04-08 13:42 ` Tino Calancha
2017-04-08 14:41 ` Philipp Stephani
2017-04-08 15:20 ` Tino Calancha
2017-04-22 19:42 ` Philipp Stephani
2017-04-08 15:38 ` npostavs
2017-04-22 19:36 ` Philipp Stephani
2017-04-05 22:03 ` Juri Linkov
2017-04-07 14:47 ` Tino Calancha
2017-04-07 15:28 ` Noam Postavsky
2017-04-07 15:54 ` Drew Adams
2017-04-08 13:49 ` Tino Calancha
2020-09-15 15:41 ` Lars Ingebrigtsen
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=alpine.DEB.2.20.1704052046350.28514@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=26338@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=mbork@mbork.pl \
/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).