From: Eli Zaretskii <eliz@gnu.org>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: 35202-done@debbugs.gnu.org
Subject: bug#35202: 27.0.50; Info-quoted false positives and false negatives
Date: Sun, 21 Apr 2019 15:02:35 +0300 [thread overview]
Message-ID: <8336mba7ms.fsf@gnu.org> (raw)
In-Reply-To: <CABczVwe9oBLKDJak0Hjn_CMwv-3dHLYXVYTqXz2GkZC=i6Qm5w@mail.gmail.com> (message from Mauro Aranda on Sat, 13 Apr 2019 10:26:19 -0300)
> From: Mauro Aranda <maurooaranda@gmail.com>
> Date: Sat, 13 Apr 2019 10:26:19 -0300
> Cc: 35202@debbugs.gnu.org
>
> > cannot be sure what to look at. Could you please specify, for each
> > spot you analyzed, the node name and the text surrounding the regexp
> > match? I'd like to go over all the places you found, but I need a
>
> Sure Eli. Sorry for not thinking about that before.
>
> In the following, navigate to the mentioned node of the respective
> manual, and either search for the string in "Search for", or just search
> for the string in "Old match". The string in "Search for" is the text
> just before the spot analyzed.
Thanks. I've proofread all these places, and installed your patch. I
also fixed a few typos that your analysis uncovered.
With that, I'm closing this bug. Thanks a lot for your work on this
tricky issue.
next prev parent reply other threads:[~2019-04-21 12:02 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8336mba7ms.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35202-done@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 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.