unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: sbaugh@catern.com
To: Juri Linkov <juri@linkov.net>
Cc: 64373@debbugs.gnu.org, Spencer Baugh <sbaugh@janestreet.com>
Subject: bug#64373: 29.0.90; C-x t o while in minibuffer copies the current tab to the next tab
Date: Fri, 30 Jun 2023 18:44:16 +0000 (UTC)	[thread overview]
Message-ID: <87a5wgokn4.fsf@catern.com> (raw)
In-Reply-To: <86mt0gdcb4.fsf@mail.linkov.net> (Juri Linkov's message of "Fri,  30 Jun 2023 21:39:43 +0300")

Juri Linkov <juri@linkov.net> writes:
>> 1. emacs -Q
>> 2. C-x t 2 to create a new tab
>> 3. C-x b *Messages* RET
>>    Now the first tab should have only *scratch* open,
>>    and the second tab should have only *Messages* open,
>>    and we're in the second tab.
>> 4. M-: (read-from-minibuffer "") RET
>> 5. While in minibuffer, C-x t o to switch to the first tab
>> 6. RET to exit minibuffer
>> 7. The first tab now has *Messages* open.
>>
>> This also applies to more complicated window configurations: the whole
>> window configuration will be copied from the tab that the minibuffer was
>> first open in, to the tab that was entered with C-x t o.
>>
>> This also happens if the minibuffer is exited with C-g.
>
> Not a bug, this is the documented behavior.
> You can customize read-minibuffer-restore-windows to nil
> if you don't like this.

We should also restore the current tab, then.  Because right now we're
restoring the window configuration, but not the current tab.

If we did that, then this would behave as expected: We'd restore the
current tab, then restore the window configuration in that tab.





  reply	other threads:[~2023-06-30 18:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 18:14 bug#64373: 29.0.90; C-x t o while in minibuffer copies the current tab to the next tab Spencer Baugh
2023-06-30 18:39 ` Juri Linkov
2023-06-30 18:44   ` sbaugh [this message]
2023-06-30 18:52     ` Juri Linkov
2023-07-03 17:18       ` Spencer Baugh
2023-07-03 18:58         ` Juri Linkov
2023-07-04 18:28     ` Juri Linkov
2023-07-05 17:21 ` Juri Linkov

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=87a5wgokn4.fsf@catern.com \
    --to=sbaugh@catern.com \
    --cc=64373@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=sbaugh@janestreet.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 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).