unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Sat, 13 Apr 2019 11:30:15 +0300	[thread overview]
Message-ID: <831s26l33c.fsf@gnu.org> (raw)
In-Reply-To: <CABczVweeFtvBTashFacyap6jq2gCxyh1muxpxKEnh_CK3etNBw@mail.gmail.com> (message from Mauro Aranda on Wed, 10 Apr 2019 21:19:54 -0300)

> From: Mauro Aranda <maurooaranda@gmail.com>
> Date: Wed, 10 Apr 2019 21:19:54 -0300
> Cc: 35202@debbugs.gnu.org
> 
> Now for the results:
> The files that presented mismatches are the following:
> emacs (as expected, hence the bug report), calc, idlwave, mh-e, org,
> sc.
> 
> To navigate to the points, for examination, I recommend widening the
> info buffer and then goto-char.

Thanks.

I think you used some old version of the Info files, because your
buffer positions sometimes don't match at all with what I see, so I
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
better guide than just buffer position, because that depends on
various factors out of my control, like the version of Texinfo used to
generate the Info files.





  reply	other threads:[~2019-04-13  8:30 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 [this message]
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=831s26l33c.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).