From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Mauro Aranda Newsgroups: gmane.emacs.bugs Subject: bug#35202: 27.0.50; Info-quoted false positives and false negatives Date: Tue, 9 Apr 2019 14:40:48 -0300 Message-ID: References: <83sgur7lbv.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000d6f86305861c7467" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="244513"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 35202@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Apr 09 19:42:21 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hDulI-0011U9-8M for geb-bug-gnu-emacs@m.gmane.org; Tue, 09 Apr 2019 19:42:20 +0200 Original-Received: from localhost ([127.0.0.1]:47020 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hDulH-0006si-8a for geb-bug-gnu-emacs@m.gmane.org; Tue, 09 Apr 2019 13:42:19 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:49326) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hDul2-0006lJ-BI for bug-gnu-emacs@gnu.org; Tue, 09 Apr 2019 13:42:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hDul0-0003vc-Ri for bug-gnu-emacs@gnu.org; Tue, 09 Apr 2019 13:42:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:38388) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hDul0-0003vO-Fm for bug-gnu-emacs@gnu.org; Tue, 09 Apr 2019 13:42:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hDul0-0008Be-CC for bug-gnu-emacs@gnu.org; Tue, 09 Apr 2019 13:42:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Mauro Aranda Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 09 Apr 2019 17:42:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 35202 X-GNU-PR-Package: emacs Original-Received: via spool by 35202-submit@debbugs.gnu.org id=B35202.155483167231389 (code B ref 35202); Tue, 09 Apr 2019 17:42:02 +0000 Original-Received: (at 35202) by debbugs.gnu.org; 9 Apr 2019 17:41:12 +0000 Original-Received: from localhost ([127.0.0.1]:51929 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hDuk8-0008A9-RE for submit@debbugs.gnu.org; Tue, 09 Apr 2019 13:41:11 -0400 Original-Received: from mail-lj1-f176.google.com ([209.85.208.176]:46184) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hDuk7-00089d-3e for 35202@debbugs.gnu.org; Tue, 09 Apr 2019 13:41:07 -0400 Original-Received: by mail-lj1-f176.google.com with SMTP id h21so3520002ljk.13 for <35202@debbugs.gnu.org>; Tue, 09 Apr 2019 10:41:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ccQjTs/rnMU5OIhmI9JtbycarKH3UMcaJ22aADeZc/s=; b=tH4fd8HbvXISX+/laaRNOF2n4phk1Alun3jOmdx+LquTwWToas0PFA0WfpHiuT/XNy cz/VDAZnrhA+d0RZeGXjuHL5w8LI4W7iHvMaKI49JnWmMwEFK1llcICmaPmwTb7zT2bo mW/1L/X76VkYvqzVJTjKsExc96X5rIEmGTZWobqRFG4dtKEHakOMwyIptzDWkwY19OsK zdoBJJiejjBx/Y/opP/tFpv3DcB4cdQnp2RejkOM6ea+9VkNa7xZz4zUIokHlHSXTHYm MDjGzA1mvn6DiA8TWc6OdbfXoD24ohKXXjXW89UTI7ZcWPIxnsGa44mfOepSdoXtbTgs wKVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ccQjTs/rnMU5OIhmI9JtbycarKH3UMcaJ22aADeZc/s=; b=GMlngciNSyZLzt3QXpk7YulKLu5v7eLC0J+/7R8jxjl8cTdR61OHxL5KxSWp+XDnPc m0Timkf5GK7q/mF5FZflJLsZ0mjOXP0/NaQqY52jfUkr6Ig4vBl9YTFYUtDZKb8wOZJG dnJTSLMXkq3Qk2w7/jomb7/O/GrRfK/0j6vHwOFSTb2FcpFB0pHTpCS6dHQSLpZyIJJP UHYaSomBik2qjOfaef8R8ccrHg4TE0CyV81uatcB7p0xciG0xjdp45iD6nsvwmM3vcMM qSQS5iivtbI/Uhxwau97Xdo7einJZ2o164dF3gywtUoA4744r+it0+3uCabKGDTtIbfc dkNw== X-Gm-Message-State: APjAAAWYGAWsuz8kbcllKRo9qTqrXMF53CPIgd9Bj/Syuk9UqlRhTYTw MD4gT3Qeho/9LWR0dI872zXVYV6xJ+dYqF8LzOM= X-Google-Smtp-Source: APXvYqzTL6vWbCcOPrmtmhfyziTlRlCccr7IJBGXLwY3JbIMRDpbQ2R4n5/J+Q0GAwmJWoJzX7M4yOJ9vCe6K9CqdCo= X-Received: by 2002:a2e:8446:: with SMTP id u6mr19729107ljh.71.1554831661002; Tue, 09 Apr 2019 10:41:01 -0700 (PDT) In-Reply-To: <83sgur7lbv.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:157424 Archived-At: --000000000000d6f86305861c7467 Content-Type: text/plain; charset="UTF-8" > Thanks, but I'm worried how we will be able to make sure this change > doesn't break display in some other places. Would it make sense to > search all our Info files for the new regexp, and examine the display > of all the places that match? Or did you already do that? > . Hello Eli. I must admit, I didn't check thoroughly, so I can't be sure it doesn't break the font-locking of quotes in other places. 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? --000000000000d6f86305861c7467 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> Thanks, but I'm worried how we w= ill be able to make sure this change
> doesn't break display in s= ome other places.=C2=A0 Would it make sense to
> search all our Info = files for the new regexp, and examine the display
> of all the places= that match?=C2=A0 Or did you already do that?
> .

Hello Eli.<= br>
I must admit, I didn't check thoroughly, so I can't be sure = it doesn't
break the font-locking of quotes in other places.

= I have come up with the following way of testing a new regexp:
Step 1: I= n Info files that come with Emacs, search the original
regexp and the ne= w regexp for all the matches.=C2=A0 Compare both results,
discarding the= insersecting values (IOW, discard the matches for which a
new regexp wo= uldn't introduce new behavior).

Step 2: Based on the previous, a= nalyze each new behavior, to see if a
new regexp does the right thing, o= r not.

Step 3: Accept, adjust or discard the regexp, accordingly.=C2= =A0 If not
accepted, go back to Step 1 for a new iteration.

Provi= ded the final regexp doesn't break display in other places (and
of course, improves the current behavior), would the procedu= re
I've just described be enough to trust a = change?
--000000000000d6f86305861c7467--