From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Visuwesh Newsgroups: gmane.emacs.bugs Subject: bug#58728: 29.0.50; Minibuffer does not follow tabs Date: Wed, 26 Oct 2022 07:08:08 +0530 Message-ID: <87tu3rcqkf.fsf@gmail.com> References: <87h6zvnrdl.fsf@gmail.com> <86bkpz7m2s.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23763"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 58728@debbugs.gnu.org To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Oct 26 03:39:36 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1onVOK-0005xU-6O for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 26 Oct 2022 03:39:36 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1onVNp-0005le-7d; Tue, 25 Oct 2022 21:39:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1onVNn-0005fB-Ij for bug-gnu-emacs@gnu.org; Tue, 25 Oct 2022 21:39:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1onVNn-0003wu-AL for bug-gnu-emacs@gnu.org; Tue, 25 Oct 2022 21:39:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1onVNm-0004sb-33 for bug-gnu-emacs@gnu.org; Tue, 25 Oct 2022 21:39:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Visuwesh Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 26 Oct 2022 01:39:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 58728 X-GNU-PR-Package: emacs Original-Received: via spool by 58728-submit@debbugs.gnu.org id=B58728.166674830518712 (code B ref 58728); Wed, 26 Oct 2022 01:39:02 +0000 Original-Received: (at 58728) by debbugs.gnu.org; 26 Oct 2022 01:38:25 +0000 Original-Received: from localhost ([127.0.0.1]:52717 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1onVNB-0004rk-CI for submit@debbugs.gnu.org; Tue, 25 Oct 2022 21:38:25 -0400 Original-Received: from mail-pl1-f195.google.com ([209.85.214.195]:42771) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1onVN9-0004rW-La for 58728@debbugs.gnu.org; Tue, 25 Oct 2022 21:38:24 -0400 Original-Received: by mail-pl1-f195.google.com with SMTP id c24so12613279pls.9 for <58728@debbugs.gnu.org>; Tue, 25 Oct 2022 18:38:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:user-agent :references:in-reply-to:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=4Fi+G53ZVWN/u93E/9wVSa8adFYAE2IFnGma1E/dcOY=; b=pu1wzHu22SaongLG/uSVv6I+0FqebKzdXY5cKlZofZ05tnAi04JNC1743Vl0kD/M0y fDRX4cpyP4WcGYppjSS7sRsFO0ZhkzVLFfdmJEEb9v5HBKRvt+ffrB7GeP6kehitzmTi Ec1A1XlxAHouDgwYMBd+CM5IjDvrt2Ne6Xyy0tJEDdUZxrFZ4fXn4LdSAwZZee12OSoP WrdcZLPoh/UyX6FoB/lb4hteQt/iaOwHWmcPylTo8ZxrPiOJcqumgQSKvuUbQzcuC/ns N/p7BUo9JpGTpD7z/ga0MLPH8AclWRyFHwamcSZ2WOJckVT3Kg6+QdXiC3BddawmkFiS l8Qw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:user-agent :references:in-reply-to:subject:cc:to:from:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=4Fi+G53ZVWN/u93E/9wVSa8adFYAE2IFnGma1E/dcOY=; b=cYkONyT85QiG17e+vGyX1nWrjK+n8755Ql4IQ19pmJWcqoO73QBxBOvS2gCgOABZ0E Zr9p8iKDwdnjiU0JCqymo/2WWHmPzFmbD1g48OpYy5AOzbHCOnkwLqskzPlX47k1LPrP UWHVQ7Pn+Xl4cBc5RLpx1bdyuZA52Szong0IuwiwS4dlOxyG5u7DrPW0Xsr/ycgLoKAe 4AiN+E1QZmO5tE2tjY2XDPxZct7j/w5BbOK8vvp818jXZ2tDOjYNzWksPGrEUngGYtIx RcbXmGV3sb/W3MFPDxlmUpL2lZdQ4NhBZoF5f5Mbxl8W0sKHszw7vxK68lCINt5FNbko u6Eg== X-Gm-Message-State: ACrzQf1SjRaFiAct9VUsuVqWve/tL4kLWzVLXIoyltCMrKxpGNLPPXCE l+sq+5PVCXgbik3rf6rrPTo= X-Google-Smtp-Source: AMsMyM7UBe7BnSrqBSOtBrPrA2YwRYi6LhmDl9Z8xBBuqL257aT/7ABNeezsCAEhzop1ktU+ACjkww== X-Received: by 2002:a17:903:1245:b0:178:9234:3768 with SMTP id u5-20020a170903124500b0017892343768mr382236plh.146.1666748297679; Tue, 25 Oct 2022 18:38:17 -0700 (PDT) Original-Received: from localhost ([118.185.152.162]) by smtp.gmail.com with ESMTPSA id s21-20020a170903201500b0016eef326febsm1804137pla.1.2022.10.25.18.38.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 25 Oct 2022 18:38:17 -0700 (PDT) In-Reply-To: <86bkpz7m2s.fsf@mail.linkov.net> (Juri Linkov's message of "Tue, 25 Oct 2022 22:14:03 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: "bug-gnu-emacs" Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:246183 Archived-At: [=E0=AE=9A=E0=AF=86=E0=AE=B5=E0=AF=8D=E0=AE=B5=E0=AE=BE=E0=AE=AF=E0=AF=8D = =E0=AE=85=E0=AE=95=E0=AF=8D=E0=AE=9F=E0=AF=8B=E0=AE=AA=E0=AE=B0=E0=AF=8D 25= , 2022] Juri Linkov wrote: > 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 ta= b. > > 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? I'd expect it to. The active minibuffer should travel across newly created tabs and old tabs. > 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. 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.