From: Eli Zaretskii <eliz@gnu.org>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: 35202@debbugs.gnu.org
Subject: bug#35202: 27.0.50; Info-quoted false positives and false negatives
Date: Tue, 09 Apr 2019 21:23:53 +0300 [thread overview]
Message-ID: <837ec36nra.fsf@gnu.org> (raw)
In-Reply-To: <CABczVwfXKLhoV0inC2oP+QuHE2==Q9SkkAts8frxE7vT8emBzA@mail.gmail.com> (message from Mauro Aranda on Tue, 9 Apr 2019 14:40:48 -0300)
> From: Mauro Aranda <maurooaranda@gmail.com>
> Date: Tue, 9 Apr 2019 14:40:48 -0300
> Cc: 35202@debbugs.gnu.org
>
> I have come up with the following way of testing a new regexp:
> Step 1: In Info files that come with Emacs, search the original
> regexp and the new regexp for all the matches. Compare both results,
> discarding the insersecting values (IOW, discard the matches for which a
> new regexp wouldn't introduce new behavior).
>
> Step 2: Based on the previous, analyze each new behavior, to see if a
> new regexp does the right thing, or not.
>
> Step 3: Accept, adjust or discard the regexp, accordingly. If not
> accepted, go back to Step 1 for a new iteration.
>
> Provided the final regexp doesn't break display in other places (and
> of course, improves the current behavior), would the procedure
> I've just described be enough to trust a change?
Sounds good to me, thanks.
next prev parent reply other threads:[~2019-04-09 18:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 22:42 bug#35202: 27.0.50; Info-quoted false positives and false negatives Mauro Aranda
2019-04-08 23:30 ` Mauro Aranda
2019-04-09 6:18 ` Eli Zaretskii
2019-04-09 17:40 ` Mauro Aranda
2019-04-09 18:23 ` Eli Zaretskii [this message]
2019-04-11 0:19 ` Mauro Aranda
2019-04-13 8:30 ` Eli Zaretskii
2019-04-13 13:26 ` Mauro Aranda
2019-04-21 12:02 ` Eli Zaretskii
2019-04-21 14:17 ` Mauro Aranda
2019-04-09 11:35 ` Noam Postavsky
2019-04-09 17:43 ` Mauro Aranda
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837ec36nra.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35202@debbugs.gnu.org \
--cc=maurooaranda@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).