From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tom Tromey <tom@tromey.com>
Cc: 32683@debbugs.gnu.org
Subject: bug#32683: 26.1.50; multi-occur-in-matching-buffers defaults could be improved
Date: Sat, 13 Jul 2019 04:37:14 +0200 [thread overview]
Message-ID: <87zhlizmlh.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87ftyhtnm0.fsf@tromey.com> (Tom Tromey's message of "Mon, 10 Sep 2018 08:48:23 -0600")
Tom Tromey <tom@tromey.com> writes:
> First, it does not provide a default for the file name regexp.
> I think it would be nice if it used the same logic as M-x rgrep.
>
> Second, it uses the file name regexp as the default search regexp.
> This is not a very good default. Again, following rgrep and using the
> word under point would be better.
Yes, the rgrep defaults seem more intuitive... but
multi-occur-in-matching-buffers is part of the "Occur" framework and
works more like those functions.
> Finally, multi-occur-in-matching-buffers asks for the file name regexp
> first and the search regexp second; whereas rgrep and lrgrep do this in
> the other order. I think it would be nice if they were all consistent.
It would, but I don't think this is possible at this date -- the command
in question is at least a decade old. So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-13 2:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 14:48 bug#32683: 26.1.50; multi-occur-in-matching-buffers defaults could be improved Tom Tromey
2019-07-13 2:37 ` Lars Ingebrigtsen [this message]
2019-07-13 2:46 ` Tom Tromey
2019-07-13 13:56 ` Lars Ingebrigtsen
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=87zhlizmlh.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=32683@debbugs.gnu.org \
--cc=tom@tromey.com \
/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).