From: "Bob Floyd" <bobfloyd@comcast.net>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 48628@debbugs.gnu.org
Subject: bug#48628: tags-search fails to find all occurences and finds one that it shouldn't
Date: Sun, 6 Jun 2021 11:05:41 -0700 [thread overview]
Message-ID: <007c01d75afe$907811e0$b16835a0$@net> (raw)
In-Reply-To: <83a6o3i37q.fsf@gnu.org>
Super! Do you have a URL explaining how to download and compile the master
branch for Windows?
-----Original Message-----
From: Eli Zaretskii [mailto:eliz@gnu.org]
Sent: Sunday, June 6, 2021 5:32 AM
To: bobfloyd@comcast.net
Cc: 48628@debbugs.gnu.org
Subject: Re: bug#48628: tags-search fails to find all occurences and finds
one that it shouldn't
> Date: Sun, 06 Jun 2021 14:01:34 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 48628@debbugs.gnu.org
>
> > From: "Bob Floyd" <bobfloyd@comcast.net>
> > Date: Mon, 24 May 2021 09:02:54 -0700
> >
> > 11. M-, (fileloop-continue) until reaching "All files processed"
> >
> > The matches are on lines:
> >
> > 7, 25, 85, 102, 115, 121
> >
> > NOTE 115 is wrong, it is this line that does not contain "_cu"
>
> With today's master branch, I'm unable to reproduce the problem: I
> don't get the false match on line 115.
However, I did spot a problem in these commands: a new tags-search
will not always start searching in each buffer from the beginning,
sometimes it will restart from the last place point was displayed for
this buffer. So I fixed that problem on the master branch now.
next prev parent reply other threads:[~2021-06-06 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 16:02 bug#48628: tags-search fails to find all occurences and finds one that it shouldn't Bob Floyd
2021-05-24 16:33 ` Eli Zaretskii
2021-05-24 16:48 ` Bob Floyd
2021-06-06 11:01 ` Eli Zaretskii
2021-06-06 12:31 ` Eli Zaretskii
2021-06-06 18:05 ` Bob Floyd [this message]
2021-06-06 18:10 ` Eli Zaretskii
2021-06-06 18:03 ` Bob Floyd
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='007c01d75afe$907811e0$b16835a0$@net' \
--to=bobfloyd@comcast.net \
--cc=48628@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.