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: Tue, 25 Oct 2022 22:14:03 +0300 [thread overview]
Message-ID: <86bkpz7m2s.fsf@mail.linkov.net> (raw)
In-Reply-To: <87h6zvnrdl.fsf@gmail.com> (Visuwesh's message of "Sun, 23 Oct 2022 09:06:06 +0530")
> I'm not sure if this qualifies as a bug or as a feature request but:
> minibuffers should follow tabs like they follow frames. To reproduce,
>
> 1. emacs -Q
> 2. C-x t 2
> 3. M-x
> 4. C-x t o
>
> Observe how the minibuffer is not active in this tab so you can't
> complete your query. You need to switch back to the tab where the M-x
> command was run to get back the minibuffer.
> [ The current behaviour makes for really confusing behaviour when
> recursive minibuffers are involved. ]
Currently the only code that handles the active minibuffer
is in tab-bar-new-tab-to:
;; Handle the case when it's called in the active minibuffer.
(when (minibuffer-selected-window)
(select-window (minibuffer-selected-window)))
that ensures that the minibuffer is not selected before creating a new tab.
So should the new feature handle all cases: when a new tab is created and
when switching existing tabs? In both cases the minibuffer should follow
the selected tab?
Currently selecting a tab just restores its window-configuration.
Should it activate the same minibuffer that was active in a previous tab?
What if two tabs have separate minibuffers? Which minibuffer wins?
In a test case:
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.
next prev parent reply other threads:[~2022-10-25 19:14 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 [this message]
2022-10-26 1:38 ` Visuwesh
2022-10-27 7:52 ` Juri Linkov
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=86bkpz7m2s.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.