unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 35352@debbugs.gnu.org
Subject: bug#35352: 26.2; Xref: (1) no activity indication, (2) no other-window opening
Date: Tue, 22 Jun 2021 17:15:57 +0200	[thread overview]
Message-ID: <87h7hqnd5e.fsf@gnus.org> (raw)
In-Reply-To: <ac267a17-d674-40ee-ba9b-b653c41840ba@default> (Drew Adams's message of "Sat, 20 Apr 2019 20:05:21 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> `dired-do-find-regexp':
>
> 1. After entering the regexp there is no feedback telling you that Emacs
>    has started searching.  Nada.  If you happen to have a search that
>    takes more than a few seconds you can really begin to wonder what, if
>    anything, is going on.  Emacs convention is to say SOMETHING -
>    typically something like "Searching..." - and then to follow that up
>    with an indication when the activity is done -
>    e.g. "Searching...done".

Makes sense.  I've now made this change in Emacs 28.

> 2. There doesn't seem to be any key binding that opens a search hit in a
>    new window or frame.  I don't want Emacs to replace the source Dired
>    buffer in its window.
>
>    In my case buffer `*xref*' is in its own dedicated window, in its own
>    frame (the buffer is a special-display buffer, based on its name.
>    Perhaps such a use case wasn't tested?  Typically Emacs provides
>    _some_ key to open things in another window or frame.

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.

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?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2021-06-22 15:15 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 [this message]
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         ` bug#35352: [External] : " Drew Adams

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=87h7hqnd5e.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=35352@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).