all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Mattias Engdegård" <mattiase@acm.org>
To: "Aurélien Aptel" <aurelien.aptel+emacs@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: New rx implementation with extension constructs
Date: Thu, 5 Sep 2019 13:17:13 +0200	[thread overview]
Message-ID: <792C9C4D-4C57-4393-9E3B-6166D6A1515E@acm.org> (raw)
In-Reply-To: <CA+5B0FMtv4itpo5Qi0=JkmMe9E4vy4_Wcp=Z8+KMbDruV41Pow@mail.gmail.com>

5 sep. 2019 kl. 12.56 skrev Aurélien Aptel <aurelien.aptel+emacs@gmail.com>:
> 
> Is this fully compatible with rx?

Yes, that is the intention. If you find an incompatibility, please report it. The compatibility includes the old `rx-constituents'  variable for extensions, which is used by python-mode.

The new implementation is slightly more general where this made sense. For instance, several forms that require at least one argument in current rx can be used with zero args in the new code. (This includes the `rx' macro itself.)

Other than that, and the new extension mechanism, I've resisted the temptation to add features, but I have a list of things that would be useful to put in later on.




  reply	other threads:[~2019-09-05 11:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02 21:19 New rx implementation with extension constructs Mattias Engdegård
2019-09-04 14:18 ` Mattias Engdegård
2019-09-04 17:03   ` Paul Eggert
2019-09-05 10:56     ` Aurélien Aptel
2019-09-05 11:17       ` Mattias Engdegård [this message]
2019-09-05 12:34         ` immerrr again
2019-09-05 19:04           ` Mattias Engdegård
2019-09-05 15:38   ` Noam Postavsky
2019-09-05 16:49     ` Mattias Engdegård
2019-09-06 14:09 ` Mattias Engdegård
2019-09-07 14:13   ` Noam Postavsky
     [not found]     ` <0E5A5E92-E48F-4003-A742-508663BA984A@acm.org>
2019-09-11 18:11       ` Mattias Engdegård
2019-09-17 12:53         ` Mattias Engdegård

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=792C9C4D-4C57-4393-9E3B-6166D6A1515E@acm.org \
    --to=mattiase@acm.org \
    --cc=aurelien.aptel+emacs@gmail.com \
    --cc=emacs-devel@gnu.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.