GNU bug report logs - #47918
M-x occur should jump to the first match

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 47918 in the body.
You can then email your comments to 47918 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: bug-gnu-emacs <at> gnu.org
Subject: M-x occur should jump to the first match
Date: Wed, 21 Apr 2021 04:11:02 +0800

occur is an interactive compiled Lisp function in ‘replace.el’.

Odd that it doesn't jump to the first match like other similar emacs
functions do.

So it should, unless the user disables it via a variable.

Message #8 received at 47918 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 47918 <at> debbugs.gnu.org
Subject: Re: bug#47918: M-x occur should jump to the first match
Date: Tue, 20 Apr 2021 15:24:58 -0500

tags 47918 wontfix notabug
close 47918
thanks

積丹尼 Dan Jacobson <jidanni <at> jidanni.org> writes:

> occur is an interactive compiled Lisp function in ‘replace.el’.
>
> Odd that it doesn't jump to the first match like other similar emacs
> functions do.
>
> So it should, unless the user disables it via a variable.

That would break existing workflows.  Also, `rgrep' and `compile'
doesn't jump to the first match, so I don't see why `occur' should be
different.

If you want to do this, I recommend:

    (add-hook 'occur-hook #'next-error)

Closing as wontfix.

Message #15 received at 47918 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: 47918 <at> debbugs.gnu.org,
 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Subject: Re: bug#47918: M-x occur should jump to the first match
Date: Wed, 21 Apr 2021 19:54:35 +0300

> That would break existing workflows.  Also, `rgrep' and `compile'
> doesn't jump to the first match, so I don't see why `occur' should be
> different.

There is 'compilation-auto-jump-to-first-error',
but it doesn't visit matches.

> If you want to do this, I recommend:
>
>     (add-hook 'occur-hook #'next-error)

This is a nice solution to immediately visit matches.

Message #18 received at 47918 <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: Juri Linkov <juri <at> linkov.net>
Cc: 47918 <at> debbugs.gnu.org, Stefan Kangas <stefan <at> marxist.se>
Subject: Re: bug#47918: M-x occur should jump to the first match
Date: Mon, 03 May 2021 22:06:11 +0800

>>>>> "JL" == Juri Linkov <juri <at> linkov.net> writes:

>> (add-hook 'occur-hook #'next-error)

Nifty! Sure wish the occur docstring in replace.el, and perhaps even
(info "(emacs) Other Repeating Search")
would mention that.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.