GNU bug report logs -
#43715
28.0.50; Duplicate results in project-find-regexp
Previous Next
Reported by: Pankaj Jangid <pankaj <at> codeisgreat.org>
Date: Wed, 30 Sep 2020 07:02:02 UTC
Severity: normal
Merged with 36967
Found in versions 27.0.50, 28.0.50
Fixed in version 28.1
Done: Dmitry Gutov <dgutov <at> yandex.ru>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> Date: Fri, 02 Oct 2020 12:18:54 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: larsi <at> gnus.org, pankaj <at> codeisgreat.org, 43715 <at> debbugs.gnu.org
>
> > Cc: larsi <at> gnus.org, pankaj <at> codeisgreat.org, 43715 <at> debbugs.gnu.org
> > From: Dmitry Gutov <dgutov <at> 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.
This bug report was last modified 4 years and 210 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.