From: Tino Calancha <tino.calancha@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 26338@debbugs.gnu.org, npostavs@users.sourceforge.net,
Marcin Borkowski <mbork@mbork.pl>,
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: Sat, 8 Apr 2017 13:45:49 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1704081338250.3238@calancha-pc> (raw)
In-Reply-To: <943bd0fd-c4ad-48f4-a803-f832b5bf0edf@default>
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. We already point out in the
manual that these are Emacs specific things, so nobody should be fooled
with that. As far as we cover all CL clauses, what problem could be in
having a few more?
I find interesting be able to do things like the following:
--8<-----------------------------cut here---------------start------------->8---
(require 'find-lisp)
(let ((op "defun")
(dir (expand-file-name "lisp" source-directory)))
(setq funcs
(cl-loop for f in (find-lisp-find-files dir "\.el\\'") nconc
(with-temp-buffer
(insert-file-contents-literally f)
(let ((regexp (format "^(%s \\(\\S +\\)" op)))
(cl-loop for x the matches of regexp using '(group 1) collect x)))))
(length funcs))
=> 38898 ; op: defun
=> 1256 ; op: defmacro
=> 1542 ; op: defsubst
--8<-----------------------------cut here---------------end--------------->8---
next prev parent reply other threads:[~2017-04-08 4:45 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 [this message]
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.1704081338250.3238@calancha-pc \
--to=tino.calancha@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 \
/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).