unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@linkov.net>
Cc: 52491@debbugs.gnu.org
Subject: bug#52491: 28.0.90; Regression in window deletion with minibuffer
Date: Wed, 22 Dec 2021 10:23:16 +0100	[thread overview]
Message-ID: <87ea2478-44f6-31ce-161f-faa2fcb917e2@gmx.at> (raw)
In-Reply-To: <86tuf17ow3.fsf@mail.linkov.net>

 > BTW, could you suggest where to look to fix such problem: for example,
 > create a grep/occur buffer, then start visiting occurrences from it
 > one by one, e.g. type RET that shows the occurrence in the second window,
 > then select the first window again, then type RET again to visit the
 > next file in the second window, etc.  Then invoke 'quit-window' in the
 > last visited buffer - it selects the first window.  Then select the
 > previous buffer in the second window, and again invoke 'quit-window'.
 > Now it removes the buffer, but doesn't select the first window.
 >
 > Such inconsistency causes a lot of trouble because of this
 > unpredictable behavior.  It reselects another window only
 > on the first invocation of 'quit-window' in the same window.
 >
 > Would it be possible either to always select another window
 > on every 'quit-window', or to never select another window
 > on 'quit-window'?

I would need a precise recipe with Emacs -Q to look into this.  I never
use *grep* buffers and when trying it in a one-window frame showing
*grep*, it pops up a new window for the first occurrence, reuses that
window for further occurrences and deletes that window when invoking
'quit-window'.

martin





  reply	other threads:[~2021-12-22  9:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 21:08 bug#52491: 28.0.90; Regression in window deletion with minibuffer Juri Linkov
2021-12-16 17:28 ` Juri Linkov
2021-12-16 17:50   ` Eli Zaretskii
2021-12-16 19:02     ` Juri Linkov
2021-12-16 20:05       ` Eli Zaretskii
2021-12-17  8:25         ` Juri Linkov
2021-12-17 12:04           ` Eli Zaretskii
2021-12-18  9:05             ` martin rudalics
2021-12-18 17:20               ` Juri Linkov
2021-12-19 10:14                 ` martin rudalics
2021-12-19 17:14                   ` Juri Linkov
2021-12-19 18:16                     ` martin rudalics
2021-12-19 18:25                       ` Juri Linkov
2021-12-20  9:18                         ` martin rudalics
2021-12-20 17:29                           ` Eli Zaretskii
2021-12-20 18:08                             ` martin rudalics
2021-12-20 18:18                               ` Eli Zaretskii
2021-12-21  8:05                               ` Juri Linkov
2021-12-21 10:33                                 ` martin rudalics
2021-12-21 19:13                                   ` Juri Linkov
2021-12-22  9:23                                     ` martin rudalics [this message]
2021-12-21  8:08                           ` Juri Linkov
2021-12-21 10:34                             ` martin rudalics

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=87ea2478-44f6-31ce-161f-faa2fcb917e2@gmx.at \
    --to=rudalics@gmx.at \
    --cc=52491@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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).