emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#34373: closed (26.1; Missing range check in rx-sub


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#34373: closed (26.1; Missing range check in rx-submatch-n)
Date: Sun, 23 Jun 2019 18:35:02 +0000

Your message dated Sun, 23 Jun 2019 20:34:07 +0200
with message-id <address@hidden>
and subject line Re: bug#34373: Acknowledgement (26.1; Missing range check in 
rx-submatch-n)
has caused the debbugs.gnu.org bug report #34373,
regarding 26.1; Missing range check in rx-submatch-n
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
34373: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=34373
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 26.1; Missing range check in rx-submatch-n Date: Thu, 7 Feb 2019 19:01:33 +0100
`rx' should protect its own abstractions and never generate an invalid regexp, 
but will if given a bad submatch number:

(rx (group-n 0 "x"))
=> "\\(?0:x\\)"

It's a missing range check in rx-submatch-n.

In GNU Emacs 26.1 (build 1, x86_64-apple-darwin14.5.0, NS appkit-1348.17 
Version 10.10.5 (Build 14F2511))
 of 2018-05-31 built on builder10-10.porkrind.org
Windowing system distributor 'Apple', version 10.3.1671




--- End Message ---
--- Begin Message --- Subject: Re: bug#34373: Acknowledgement (26.1; Missing range check in rx-submatch-n) Date: Sun, 23 Jun 2019 20:34:07 +0200
23 juni 2019 kl. 20.20 skrev Lars Ingebrigtsen <address@hidden>:
> 
> This looks like an eminently reasonable sanity check to me, but I'm
> quite unfamiliar with the rx machinery.  Just push the change?

Thank you, pushed.



--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]