From: Philipp Stephani <p.stephani2@gmail.com>
To: Tino Calancha <tino.calancha@gmail.com>,
Drew Adams <drew.adams@oracle.com>
Cc: 26338@debbugs.gnu.org, npostavs@users.sourceforge.net,
Marcin Borkowski <mbork@mbork.pl>, Juri Linkov <juri@linkov.net>
Subject: bug#26338: 26.0.50; Collect all matches for REGEXP in current buffer
Date: Sat, 08 Apr 2017 11:46:50 +0000 [thread overview]
Message-ID: <CAArVCkQUhwtCF786EXjp2XghvU-+dOL1=mKVxTOz0j13bQkpow@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1704081338250.3238@calancha-pc>
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
Tino Calancha <tino.calancha@gmail.com> schrieb am Sa., 8. Apr. 2017 um
06:46 Uhr:
>
>
> On Fri, 7 Apr 2017, Drew Adams wrote:
>
> >>> 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.
> >>
> >> Your proposals looks nice to me ;-)
> >
> > (Caveat: I have not been following this thread.)
> >
> > I think that `cl-loop' should be as close to Common Lisp `loop'
> > as we can reasonably make it. We should _not_ be adding other
> > features to it or changing its behavior away from what it is
> > supposedly emulating.
> >
> > If you want, create a _different_ macro that is Emacs-specific,
> > with whatever behavior you want. Call it whatever you want
> > that will not be confused with Common Lisp emulation.
> >
> > Please keep `cl-' for Common Lisp emulation. We've already
> > seen more than enough tampering with this - people adding
> > their favorite thing to the `cl-' namespace. Not good.
> Drew, i respect your opinion; but so far the change
> would just extend `cl-loop' which as you noticed has being already
> extended before.
> For instance, we have:
> cl-loop for x being the overlays/buffers ...
>
> Don't see a problem to have those things.
I do. They couple the idea of an iterable with a looping construct, and
such coupling is bad for various reasons:
- Coupling of unrelated entities is always an antipattern.
- For N iterables and M looping constructs, you need to implement N*M
integrations.
Instead this should use an iterable, e.g. a generator function
(iter-defun). cl-loop supports these out of the box.
[-- Attachment #2: Type: text/html, Size: 2939 bytes --]
next prev parent reply other threads:[~2017-04-08 11:46 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAArVCkQUhwtCF786EXjp2XghvU-+dOL1=mKVxTOz0j13bQkpow@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=26338@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=juri@linkov.net \
--cc=mbork@mbork.pl \
--cc=npostavs@users.sourceforge.net \
--cc=tino.calancha@gmail.com \
/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.