From: Juri Linkov <juri@linkov.net>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] New tab-bar-detach-tab command
Date: Sun, 03 Oct 2021 20:19:18 +0300 [thread overview]
Message-ID: <87k0iu6n6x.fsf@mail.linkov.net> (raw)
In-Reply-To: <871r57i2cz.fsf@alphapapa.net> (Adam Porter's message of "Wed, 29 Sep 2021 14:54:52 -0500")
>> Also I fixed another issue noted by Matt:
>> “tab-close: Attempt to delete the sole tab in a frame”.
>> This is fixed now to delete the whole frame when its last tab
>> was moved to another frame.
Another small fix was needed to handle the case when the window manager
immediately selects the new frame created by `make-frame'.
>>>> Currently I'm developing a command that will detach a window
>>>> to a new tab, i.e. it will delete the selected window
>>>> from the current tab after moving it to the new tab.
>>>> And I'd like to add a keybinding to it with the same mnemonics "D" :-)
>>>
>>> Hm, what if the new window-detaching command were on "C-x t d", and the
>>> new tab-detaching command were on "C-x t D"? Of course, "C-x t d" is
>>> currently bound to 'dired-other-tab', but it seems like that should be
>>> covered by 'other-tab-prefix', i.e. "C-x t t C-x d".
>>
>> 'C-x t d' was modeled after 'C-x 5 d' (dired-other-frame),
>> and since I use 'C-x t d' all the time, I expect that other users
>> might be accustomed to it as well. We need to find a new key
>> or better a key prefix to accommodate more future keys.
>
> Makes sense. Thanks.
The new window-detaching command is implemented now, but still
no idea where to bind these commands: tab-detaching and window-detaching.
next prev parent reply other threads:[~2021-10-03 17:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 19:09 [PATCH] New tab-bar-detach-tab command Adam Porter
2021-09-29 1:05 ` Matt Beshara
2021-09-29 7:11 ` Juri Linkov
2021-09-29 7:43 ` Adam Porter
2021-09-29 7:09 ` Juri Linkov
2021-09-29 7:59 ` Adam Porter
2021-09-29 19:43 ` Juri Linkov
2021-09-29 19:54 ` Adam Porter
2021-10-03 17:19 ` Juri Linkov [this message]
2021-10-04 10:34 ` Adam Porter
2021-10-04 17:33 ` Juri Linkov
2021-10-04 19:53 ` Adam Porter
2021-10-05 6:49 ` Juri Linkov
2021-10-05 7:17 ` Adam Porter
2021-10-05 15:27 ` [External] : " Drew Adams
2021-10-05 16:38 ` Juri Linkov
2021-10-06 11:23 ` Adam Porter
2021-10-06 16:38 ` Juri Linkov
2021-10-07 18:02 ` Juri Linkov
2021-10-07 18:23 ` [External] : " Drew Adams
2021-10-05 15:18 ` Drew Adams
2021-10-05 16:40 ` Juri Linkov
2021-10-05 17:27 ` Drew Adams
2021-10-06 16:39 ` Juri Linkov
2021-10-06 20:20 ` [External] : " Drew Adams
2021-10-07 7:29 ` Juri Linkov
2021-10-07 7:43 ` Eli Zaretskii
2021-10-07 17:58 ` Juri Linkov
2021-10-07 18:19 ` Drew Adams
2021-10-07 18:28 ` Eli Zaretskii
2021-10-07 15:56 ` Drew Adams
2021-10-05 16:35 ` Juri Linkov
2021-10-05 15:15 ` [External] : " Drew Adams
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=87k0iu6n6x.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
/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.