From: Visuwesh <visuweshm@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 58728@debbugs.gnu.org
Subject: bug#58728: 29.0.50; Minibuffer does not follow tabs
Date: Thu, 27 Oct 2022 19:52:23 +0530 [thread overview]
Message-ID: <87tu3p2vog.fsf@gmail.com> (raw)
In-Reply-To: <86ilk5vh3w.fsf@mail.linkov.net> (Juri Linkov's message of "Thu, 27 Oct 2022 10:52:03 +0300")
[வியாழன் அக்டோபர் 27, 2022] Juri Linkov wrote:
>>> 1. emacs -Q
>>> 2. C-x t 2
>>> 3. M-x
>>> 4. C-x t o
>>> 5. M-:
>>> 6. C-x t o
>>>
>>> what minibuffer should be displayed? Probably the last.
>>
>> I think showing the most "recent" minibuffer should be shown. If we go
>> by minibuffer-depth-indicate-mode, then the most "recent" minibuffer
>> would be the labelled 2.
>
> As soon as someone will point out to a function that does this,
> it could be immediately added to tab-bar.el. What is needed is
> something to work in such situation:
>
> 1. emacs -Q
> 2. M-: (setq wc (current-window-configuration))
> 3. M-x
> 4. M-: (set-window-configuration wc)
> 5. ???
> 6. The minibuffer with its window is restored and reactivated.
>
> Maybe something like what frameset-to-register/jump-to-register does,
> that restores the minibuffer, but doesn't reactivate it.
Without putting much effort, I ended up with the following expression
after a quick C-h d for "minibuffer"
(set-window-buffer (minibuffer-window) (get-buffer (format " *Minibuf-%d*" (minibuffer-depth))))
I am not sure how well this will work with minibuffer-only-frames and
such though. We need to select the minibuffer when switching the tab if
the minibuffer was selected prior to the switch too, but that's a matter
of (select-window (minibuffer-window)) I think.
next prev parent reply other threads:[~2022-10-27 14:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 3:36 bug#58728: 29.0.50; Minibuffer does not follow tabs Visuwesh
2022-10-24 18:54 ` Sean Whitton
2022-10-25 19:17 ` Juri Linkov
2022-10-25 19:14 ` Juri Linkov
2022-10-26 1:38 ` Visuwesh
2022-10-27 7:52 ` Juri Linkov
2022-10-27 14:22 ` Visuwesh [this message]
2022-10-28 6:40 ` Juri Linkov
2022-10-28 7:20 ` Juri Linkov
2022-10-29 16:17 ` Visuwesh
2022-10-30 7:34 ` Juri Linkov
2022-10-30 13:50 ` Visuwesh
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=87tu3p2vog.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=58728@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).