From: Juri Linkov <juri@linkov.net>
To: Visuwesh <visuweshm@gmail.com>
Cc: 58728@debbugs.gnu.org
Subject: bug#58728: 29.0.50; Minibuffer does not follow tabs
Date: Thu, 27 Oct 2022 10:52:03 +0300 [thread overview]
Message-ID: <86ilk5vh3w.fsf@mail.linkov.net> (raw)
In-Reply-To: <87tu3rcqkf.fsf@gmail.com> (Visuwesh's message of "Wed, 26 Oct 2022 07:08:08 +0530")
>> 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.
next prev parent reply other threads:[~2022-10-27 7:52 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 [this message]
2022-10-27 14:22 ` Visuwesh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ilk5vh3w.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=58728@debbugs.gnu.org \
--cc=visuweshm@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.