From: Eli Zaretskii <eliz@gnu.org>
To: dgutov@yandex.ru
Cc: larsi@gnus.org, pankaj@codeisgreat.org, 43715@debbugs.gnu.org
Subject: bug#43715: 28.0.50; Duplicate results in project-find-regexp
Date: Fri, 02 Oct 2020 12:52:33 +0300 [thread overview]
Message-ID: <83k0w9eyzi.fsf@gnu.org> (raw)
In-Reply-To: <83mu15f0jl.fsf@gnu.org> (message from Eli Zaretskii on Fri, 02 Oct 2020 12:18:54 +0300)
> Date: Fri, 02 Oct 2020 12:18:54 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: larsi@gnus.org, pankaj@codeisgreat.org, 43715@debbugs.gnu.org
>
> > Cc: larsi@gnus.org, pankaj@codeisgreat.org, 43715@debbugs.gnu.org
> > From: Dmitry Gutov <dgutov@yandex.ru>
> > Date: Fri, 2 Oct 2020 11:52:49 +0300
> >
> > >> So you think it's a good idea for 'n' and 'p' to skip subsequent matches
> > >> on the line?
> > >
> > > Please don't: that would be mightily confusing.
> >
> > To play the devil's advocate: this is already what both Grep and Occur
> > do. So maybe it is fine?
> >
> > Or we should fix the other modes.
>
> I'd prefer the latter, of course.
At least by default, that is. If someone really wants to be able to
skip identical hits, I won't object to having an option for that. But
having 'n' and 'p' skip by default is unexpected and confusing.
prev parent reply other threads:[~2020-10-02 9:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 7:01 bug#43715: 28.0.50; Duplicate results in project-find-regexp Pankaj Jangid
2020-09-30 13:59 ` Lars Ingebrigtsen
2020-09-30 19:25 ` Juri Linkov
2020-09-30 22:52 ` Dmitry Gutov
2020-10-01 1:15 ` Lars Ingebrigtsen
2020-10-01 20:38 ` Dmitry Gutov
2020-10-01 20:39 ` Lars Ingebrigtsen
2020-10-01 21:28 ` Dmitry Gutov
2020-10-01 21:30 ` Dmitry Gutov
2020-10-01 21:38 ` Lars Ingebrigtsen
2020-10-01 21:45 ` Dmitry Gutov
2020-10-02 6:37 ` Eli Zaretskii
2020-10-02 8:52 ` Dmitry Gutov
2020-10-02 9:18 ` Eli Zaretskii
2020-10-02 9:52 ` Eli Zaretskii [this message]
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=83k0w9eyzi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43715@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=larsi@gnus.org \
--cc=pankaj@codeisgreat.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 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).