From: Michael Heerdegen <michael_heerdegen@web.de>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: xr
Date: Fri, 01 Mar 2019 16:25:44 +0100 [thread overview]
Message-ID: <8736o6sjk7.fsf@web.de> (raw)
In-Reply-To: <99EEC0DC-3E76-4CC7-80D7-B6ADF480C818@acm.org> ("Mattias \=\?utf-8\?Q\?Engdeg\=C3\=A5rd\=22's\?\= message of "Thu, 28 Feb 2019 15:10:54 +0100")
Mattias Engdegård <mattiase@acm.org> writes:
> Good defaults are just as important. I thought that one-or-more would
> be more descriptive than + or 1+ for those not familiar with the rx
> notation, but perhaps this was a mistake.
Not a mistake, not just what everybody wants. Dunno what the majority
wants. But I think as a default it could be right, because it's
something at least everybody understands.
> Which would you prefer as default symbol from each of these sets?
I didn't bother with regexps very often, so count my opinion as the
opinion of some random user.
> one-or-more 1+ +
> zero-or-more 0+ *
> zero-or-one optional opt ?
+, *, ?, because they are short and what I'm used to from string regexps.
> repeat ** (for lower-upper-bounded repetition)
> repeat = (for exact-count repetition)
> any char in
> not-newline nonl
> group submatch
Don't have preferences yet here.
> line-start bol
> line-end eol
> string-start buffer-start bos bot
> string-end buffer-end eos eot
> word-start bow
> word-end eow
bol, eol, bos, eos, bow, eow: short and easy to remember.
> sequence seq and :
I guess seq.
> or |
|.
> regexp regex
I always look up which is the right one. Oh - they work both? Cool.
Michael.
prev parent reply other threads:[~2019-03-01 15:25 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 14:09 [ELPA] New package: xr Mattias Engdegård
2019-02-01 15:25 ` Clément Pit-Claudel
2019-02-01 15:42 ` Eli Zaretskii
2019-02-01 18:39 ` Clément Pit-Claudel
2019-02-01 15:51 ` Mattias Engdegård
2019-02-01 18:41 ` Clément Pit-Claudel
2019-02-02 9:43 ` Mattias Engdegård
2019-02-02 15:15 ` Mattias Engdegård
2019-02-02 18:41 ` Clément Pit-Claudel
2019-02-03 9:37 ` Mattias Engdegård
2019-02-03 20:11 ` Juri Linkov
2019-02-03 21:04 ` Mattias Engdegård
2019-02-03 21:13 ` Clément Pit-Claudel
2019-02-05 16:15 ` Stefan Monnier
2019-02-05 22:37 ` Michael Heerdegen
2019-02-06 0:04 ` Mattias Engdegård
2019-02-05 23:00 ` Michael Heerdegen
2019-02-06 0:11 ` Stefan Monnier
2019-02-06 0:25 ` Noam Postavsky
2019-02-06 0:34 ` Michael Heerdegen
2019-02-06 1:36 ` Stefan Monnier
2019-02-06 12:43 ` Mattias Engdegård
2019-02-07 4:34 ` pcre2el Richard Stallman
2019-02-07 7:11 ` pcre2el John Wiegley
2019-02-07 14:54 ` pcre2el Stefan Monnier
2019-02-06 0:02 ` [ELPA] New package: xr Mattias Engdegård
2019-02-06 0:14 ` Stefan Monnier
2019-02-06 7:02 ` Richard Stallman
2019-02-06 15:39 ` Eli Zaretskii
2019-02-07 4:36 ` Richard Stallman
2019-02-07 14:37 ` Eli Zaretskii
2019-02-08 3:21 ` Richard Stallman
2019-02-08 3:50 ` Stefan Monnier
2019-02-08 7:18 ` Eli Zaretskii
2019-02-08 10:06 ` Stephen Berman
2019-02-09 3:37 ` Richard Stallman
2019-02-09 8:03 ` Eli Zaretskii
2019-02-09 3:38 ` Richard Stallman
2019-02-09 8:05 ` Eli Zaretskii
2019-02-10 5:51 ` Richard Stallman
2019-02-10 15:12 ` Eli Zaretskii
2019-02-11 5:38 ` Richard Stallman
2019-02-10 5:51 ` Richard Stallman
2019-02-10 15:14 ` Eli Zaretskii
2019-02-09 3:37 ` Richard Stallman
2019-02-27 15:06 ` Michael Heerdegen
2019-02-27 16:22 ` Mattias Engdegård
2019-02-27 17:09 ` Michael Heerdegen
2019-02-28 14:10 ` Mattias Engdegård
2019-02-28 14:34 ` Clément Pit-Claudel
2019-02-28 23:06 ` Stefan Monnier
2019-03-01 13:39 ` Mattias Engdegård
2019-03-01 13:51 ` Stefan Monnier
2019-03-01 5:29 ` Van L
2019-03-01 13:54 ` Stefan Monnier
2019-03-01 15:25 ` Michael Heerdegen [this message]
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=8736o6sjk7.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-devel@gnu.org \
--cc=mattiase@acm.org \
/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.