[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer
From: |
npostavs |
Subject: |
bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer |
Date: |
Wed, 05 Apr 2017 09:11:30 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Tino Calancha <tino.calancha@gmail.com> writes:
>
> 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.
Perhaps a macro that loops over matches?
(defmacro domatches (spec &rest body)
"Loop over matches to REGEXP.
\(fn (MATCH-VAR [GROUP] REGEXP [BOUND]) BODY...)")
Or an addition to cl-loop that would allow doing something like
(cl-loop for m being the matches of "foo\\|bar"
do ...)
Then you could easily 'collect m' to get the list of matches if you want
that.
> I will repeat it once more. I find nice, having an operator returning
> a list with matches for REGEXP.
I don't think that's come up for me very much, if at all. It seems
easier to just operate on the matches directly rather than collecting
and then mapping.
> If such operator, in addition,
> accepts a body of code or a function, then i find this operator very
> nice
> and elegant.
Forcing collection on the looping operator seems inelegant to me.
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, (continued)
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Dmitry Gutov, 2017/04/02
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Juri Linkov, 2017/04/02
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Tino Calancha, 2017/04/03
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Tino Calancha, 2017/04/03
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Juri Linkov, 2017/04/03
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Tino Calancha, 2017/04/03
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Tino Calancha, 2017/04/03
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Marcin Borkowski, 2017/04/04
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Tino Calancha, 2017/04/05
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer,
npostavs <=
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Tino Calancha, 2017/04/07
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Drew Adams, 2017/04/07
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Tino Calancha, 2017/04/08
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Drew Adams, 2017/04/08
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Tino Calancha, 2017/04/08
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Drew Adams, 2017/04/08
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Philipp Stephani, 2017/04/08
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Tino Calancha, 2017/04/08
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Philipp Stephani, 2017/04/08
- bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer, Tino Calancha, 2017/04/08