From: Jean Louis <bugs@gnu.support>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: For text processing, which is more powerful, emacs or perl?
Date: Sun, 20 Dec 2020 08:23:10 +0300 [thread overview]
Message-ID: <X97fvo16Z/kG3e7J@protected.rcdrun.com> (raw)
In-Reply-To: <jwvo8ipoke7.fsf-monnier+emacs@gnu.org>
* Stefan Monnier <monnier@iro.umontreal.ca> [2020-12-19 19:02]:
> > It's well known that perl's regexp is very powerful for its capability
> > of text processing. So, which is more powerful, emacs or perl, in this
> > scenario?
>
> Probably Snobol or Icon.
Thank you. Very interesting resource:
https://www2.cs.arizona.edu/icon/
next prev parent reply other threads:[~2020-12-20 5:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 7:43 For text processing, which is more powerful, emacs or perl? Hongyi Zhao
2020-12-19 9:00 ` Jean Louis
2020-12-19 12:17 ` Hongyi Zhao
2020-12-19 12:25 ` Jean Louis
2020-12-20 0:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-20 1:42 ` Hongyi Zhao
2020-12-20 3:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-20 5:31 ` Jean Louis
2020-12-20 6:18 ` Hongyi Zhao
2020-12-20 6:52 ` Jean Louis
2020-12-20 7:49 ` Hongyi Zhao
2020-12-20 13:42 ` Jean Louis
2020-12-20 3:03 ` Hongyi Zhao
2020-12-20 3:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-08 16:42 ` Marcin Borkowski
2020-12-19 14:36 ` Harald Jörg
2020-12-20 4:38 ` Jean Louis
2020-12-19 16:01 ` Stefan Monnier
2020-12-20 5:23 ` Jean Louis [this message]
2020-12-20 6:17 ` Hongyi Zhao
2020-12-20 6:25 ` Jean Louis
2020-12-20 13:58 ` Stefan Monnier
2020-12-20 14:47 ` tomas
2020-12-20 9:01 ` tomas
2021-10-08 16:52 ` Marcin Borkowski
2021-10-09 1:42 ` Hongyi Zhao
2021-10-10 14:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=X97fvo16Z/kG3e7J@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.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.