From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Dmitry Gutov <dgutov@yandex.ru>
Cc: "35352@debbugs.gnu.org" <35352@debbugs.gnu.org>
Subject: bug#35352: [External] : Re: bug#35352: 26.2; Xref: (1) no activity indication, (2) no other-window opening
Date: Thu, 22 Jul 2021 15:13:39 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488F4FAD953BF0CD1ED5708F3E49@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87k0liig43.fsf@gnus.org>
> >>> But... on the other hand, perhaps a standard set of commands (and
> >>> keystrokes) for these "follow this 'link'" modes would be nice? Anybody
> >>> got an opinion here?
> >>
> >> https://urldefense.com/v3/__https://elpa.gnu.org/packages/other-frame-
> window.html__;!!ACWV5N9M2RV99hQ!ZlCeUkIklYNOveRY6ugZ4ggHQ5GxNlrOzfhQlkK0u4FNb
> Goamg7I5Np4twlAb__9$ ?
> >
> > Ah, nice. There's still the question of whether Emacs should have
> > (something like) this built-in, but I'm leaning towards "no"...
Whether nice or not, that's irrelevant to this bug
report, IMO. Sure, it talks about using another
window - that's all.
> And nobody had an opinion here in a month, so
> I'm closing this bug report.
Opinion about `other-frame-window'? Not related.
Was the case of a dedicated window for the *xref*
buffer tested? That's a case I reported about.
> Well, it depends on the mode. For instance, I don't
> think `M-x grep' has any command to open in a new
> window/frame, and I don't think we want to add all
> those commands to all these modes because users want
> so many different combinations here that it's best
> left to the general buffer/window selection machinery.
You mentioned *grep* as being the _same_ as *xref*.
I wish *xref* _did_ behave like *grep. The problem
is that it doesn't.
As I said in my report, I use dedicated windows for
buffers whose names start and end with `*'. E.g.,
(setq special-display-regexps '("[ ]?[*][^*]+[*]"))
*xref* should be the same case as *grep*, but it's
not. The bug was reported for *xref*.
With grep, `RET' or `mouse-2' on a search hit invokes
`compile-goto-error', which does `next-error-internal',
which DTRT - it opens the search-hit buffer in a
window other than that of the Dired buffer.
That's the point of the bug report - a request to make
*xref* behave properly, like *grep* does, when choosing
a search hit.
If this was fixed, great; thanks. If not, then I guess
this is just another "won't fix".
prev parent reply other threads:[~2021-07-22 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-21 3:05 bug#35352: 26.2; Xref: (1) no activity indication, (2) no other-window opening Drew Adams
2019-05-28 20:43 ` Juri Linkov
2019-05-30 17:29 ` Dmitry Gutov
2021-06-22 15:15 ` Lars Ingebrigtsen
2021-06-22 15:53 ` Dmitry Gutov
2021-06-23 12:57 ` Lars Ingebrigtsen
2021-07-22 14:21 ` Lars Ingebrigtsen
2021-07-22 15:13 ` Drew Adams [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=SJ0PR10MB5488F4FAD953BF0CD1ED5708F3E49@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=35352@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=larsi@gnus.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).