all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Sun, 30 Oct 2022 19:20:20 +0530	[thread overview]
Message-ID: <874jvl2zfn.fsf@gmail.com> (raw)
In-Reply-To: <867d0hpxxk.fsf@mail.linkov.net> (Juri Linkov's message of "Sun,  30 Oct 2022 09:34:15 +0200")

[ஞாயிறு அக்டோபர் 30, 2022] Juri Linkov wrote:

>> This works exactly like I want to!  One minor nit: it does not preserve
>> the minibuffer focus so you can end up with the minibuffer selected in
>> some tabs but not in others when switching however, this is the same
>> behaviour when switching frames too so I can put up with it just fine.
>
> I don't know how to preserve the minibuffer focus in case of switching frames,
> but it was easy to implement for tabs.  So now this is pushed.  Thanks for
> helping to fix this issue.

Great thanks!

> PS: A variable corresponding to minibuffer-follows-selected-frame
> could be added too when someone will ask for it.  But currently
> I see no need for such a variable because tabs are quite different
> from frames: the active minibuffer can be visible in another frame
> as a visual reminder that there are active minibuffers, but not so
> in case of tabs when the active minibuffer is hidden in another tab.

Indeed, I agree.





      reply	other threads:[~2022-10-30 13:50 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
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 [this message]

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=874jvl2zfn.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 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.