[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#43715: 28.0.50; Duplicate results in project-find-regexp
From: |
Eli Zaretskii |
Subject: |
bug#43715: 28.0.50; Duplicate results in project-find-regexp |
Date: |
Fri, 02 Oct 2020 12:52:33 +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.
- bug#43715: 28.0.50; Duplicate results in project-find-regexp, Dmitry Gutov, 2020/10/01
- bug#43715: 28.0.50; Duplicate results in project-find-regexp, Lars Ingebrigtsen, 2020/10/01
- bug#43715: 28.0.50; Duplicate results in project-find-regexp, Dmitry Gutov, 2020/10/01
- bug#43715: 28.0.50; Duplicate results in project-find-regexp, Dmitry Gutov, 2020/10/01
- bug#43715: 28.0.50; Duplicate results in project-find-regexp, Lars Ingebrigtsen, 2020/10/01
- bug#43715: 28.0.50; Duplicate results in project-find-regexp, Dmitry Gutov, 2020/10/01
- bug#43715: 28.0.50; Duplicate results in project-find-regexp, Eli Zaretskii, 2020/10/02
- bug#43715: 28.0.50; Duplicate results in project-find-regexp, Dmitry Gutov, 2020/10/02
- bug#43715: 28.0.50; Duplicate results in project-find-regexp, Eli Zaretskii, 2020/10/02
- bug#43715: 28.0.50; Duplicate results in project-find-regexp,
Eli Zaretskii <=