From: Peter Neidhardt <pe.neidhardt@googlemail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: rms@gnu.org, Noam Postavsky <npostavs@gmail.com>,
emacs-devel@gnu.org, van@scratch.space,
Alan Mackenzie <acm@muc.de>,
eliz@gnu.org
Subject: Re: rx.el sexp regexp syntax
Date: Sat, 26 May 2018 01:32:11 +0200 [thread overview]
Message-ID: <87fu2fgvlw.fsf@gmail.com> (raw)
In-Reply-To: <87k1rr78m2.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
Michael Heerdegen <michael_heerdegen@web.de> writes:
>> A string regexp, by contrast, usually fits onto a single line.
>
> But regexps are tree-like structures. That's why rx, which uses sexps
> (i.e. trees), is the easier to read representation for complicated
> regexps than a one-dimensional string. Unless you have the ability to
> form a representation in your head.
I did not think of this at first but I think it's an excellent,
fundamental point.
>> The "English" counterpart used in rx is bulky and difficult to learn.
>> Somehow, you've got to learn that it's "word-start" and not
>> "word-beginning", that it's "not" and not "non", and so on.
>
> That's IMHO the main reason why people avoid using rx. I wonder if that
> aspect of rx could be improved (why not just use $ as synonym for bol
> etc.)?
I guess you meant 'eol' ;)
rx supports synonyms and I think in general it's not a good idea.
That said, I really like that it uses meaningful words. So instead of
‘line-end’, ‘eol’
I'd leave it to only
‘line-end’
--
Peter Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-05-25 23:32 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 10:47 rx.el sexp regexp syntax (WAS: Off Topic) Noam Postavsky
2018-05-24 10:58 ` Van L
2018-05-25 2:57 ` Richard Stallman
2018-05-25 8:52 ` Pierre Neidhardt
2018-05-25 15:51 ` Alan Mackenzie
2018-05-25 16:47 ` Pierre Neidhardt
2018-05-25 18:01 ` rx.el sexp regexp syntax Eric Abrahamsen
2018-05-25 18:12 ` Pierre Neidhardt
2018-05-25 18:56 ` Eric Abrahamsen
2018-05-25 21:42 ` Clément Pit-Claudel
2018-05-25 21:51 ` Eric Abrahamsen
2018-05-25 22:27 ` Michael Heerdegen
2018-05-25 22:44 ` Eric Abrahamsen
2018-05-27 20:27 ` Stefan Monnier
2018-05-28 16:37 ` Pierre Neidhardt
2018-05-28 17:15 ` Stefan Monnier
2018-05-29 3:10 ` Richard Stallman
2018-05-29 7:28 ` Robert Pluim
2018-05-29 8:27 ` Philipp Stephani
2018-05-30 3:24 ` Richard Stallman
2018-05-30 7:25 ` Robert Pluim
2018-05-31 3:53 ` Richard Stallman
2018-05-31 8:57 ` Robert Pluim
2018-05-31 4:13 ` Clément Pit-Claudel
2018-05-31 14:19 ` Stefan Monnier
2018-05-31 15:43 ` Drew Adams
2018-05-31 16:12 ` João Távora
2018-05-31 16:18 ` Robert Pluim
2018-05-31 16:48 ` Basil L. Contovounesios
2018-05-31 17:02 ` Basil L. Contovounesios
2018-05-31 18:40 ` João Távora
2018-06-02 19:33 ` Eric Abrahamsen
2018-06-03 3:49 ` Stefan Monnier
2018-06-03 4:59 ` Eric Abrahamsen
2018-06-03 14:51 ` Helmut Eller
2018-06-03 15:15 ` Eric Abrahamsen
2018-06-03 15:53 ` Helmut Eller
2018-06-03 16:40 ` Eric Abrahamsen
2018-06-03 19:57 ` Drew Adams
2018-06-03 21:15 ` Eric Abrahamsen
2018-06-03 23:23 ` Drew Adams
2018-06-04 13:56 ` Stefan Monnier
2018-06-04 15:24 ` Drew Adams
2018-06-04 15:44 ` Pierre Neidhardt
2018-05-25 18:17 ` rx.el sexp regexp syntax (WAS: Off Topic) Alan Mackenzie
2018-05-25 20:35 ` Peter Neidhardt
2018-05-25 21:01 ` rx.el sexp regexp syntax Michael Heerdegen
2018-05-25 23:32 ` Peter Neidhardt [this message]
2018-05-27 16:56 ` Tom Tromey
2018-05-27 20:16 ` Alan Mackenzie
2018-05-27 20:23 ` Stefan Monnier
2018-05-27 20:16 ` Stefan Monnier
2018-05-28 16:36 ` Pierre Neidhardt
2018-05-28 17:04 ` Stefan Monnier
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=87fu2fgvlw.fsf@gmail.com \
--to=pe.neidhardt@googlemail.com \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=npostavs@gmail.com \
--cc=rms@gnu.org \
--cc=van@scratch.space \
/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.