From: Kalman Reti <kalman.reti@gmail.com>
To: Robert Cochran <robert+Emacs@cochranmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Enable persistent naming for tabs
Date: Wed, 23 Oct 2019 16:53:23 -0400 [thread overview]
Message-ID: <CAJ7Ts_3UOvvpsGOJA4_YWn0o8h1eXqONsvaosLqkKLEZet5=bw@mail.gmail.com> (raw)
In-Reply-To: <87d0f66fi5.fsf@cochranmail.com>
[-- Attachment #1: Type: text/plain, Size: 2405 bytes --]
ooak
On Wed, Oct 9, 2019 at 11:48 AM Robert Cochran <robert+Emacs@cochranmail.com>
wrote:
> Hi emacs-devel,
>
> I saw news recently of the new tabs that are on master. They're really
> nifty - kudos to Juri Linkov for doing a lot of work on them. :)
>
> I was admittedly a little disappointed, however, to see that the user, or
> other Lisp programs, couldn't change the name of a tab persistently - it
> *could* be changed, but a lot of the functions that handle tabs
> immediately call the automatic naming function, before the UI could even
> update to display it. Some applications might want to have a consistent
> name divorced from the current buffer, and sometimes it would be nice to
> override the automatic name on a per-tab basis as a user.
>
> The solution I went with was another value in the tabs frame-parameter
> alist. A new cons with the name `no-auto-name` in the car is used. If
> the cdr is nil, then the behavior we have now remains - the tab handling
> functions will call the value of `tab-bar-tab-name-function` and update
> the name immediately. With a non-nil value, any time
> `tab-bar-tab-name-function` would be called, the existing name is
> instead substituted.
>
> I've added 2 new functions, `tab-bar-rename-tab` and
> `tab-bar-rename-tab-by-name`. Both functions take a new name, and a tag
> identifier, either a frame tab index or an existing name,
> respectively. The new name is then set on the tab, and the
> `no-auto-name` parameter is set non-nil, unless the new name is the
> empty string, which is taken to mean 'turn automatic naming back on'.
>
> A couple of things I'm still wondering about: should this be documented
> in the manual? I was going to do so, but couldn't really find a good
> spot to mention it. If we do add something to the manual, we should
> mention `tab-bar-tab-name-function` as well. Do we want to add this to
> the default `C-x 6` binds, possibly as `C-x 6 r`? I already set
> `tab-rename` as an alias to `tab-bar-rename-tab`, but I'm curious what
> other people are thinking on that. Is there a better name for
> `no-auto-name`? I couldn't think of a better one... I was aiming to have
> a name who's interpretation as 'nil' is 'don't do anything differently',
> so as to make the code slightly easier to read, as well as ensuring
> saved tabs don't get automatic naming turned on by mistake.
>
> Thanks,
> --
> ~Robert Cochran
>
>
[-- Attachment #2: Type: text/html, Size: 2901 bytes --]
next prev parent reply other threads:[~2019-10-23 20:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 22:26 [PATCH] Enable persistent naming for tabs Robert Cochran
2019-10-09 16:02 ` Eli Zaretskii
2019-10-09 22:58 ` Juri Linkov
2019-10-23 20:53 ` Kalman Reti [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-10 1:03 Robert Cochran
2019-10-10 21:43 ` Juri Linkov
[not found] ` <87ftjz6v4d.fsf@cochranmail.com>
2019-10-13 19:53 ` Juri Linkov
2019-10-15 21:45 ` Juri Linkov
2019-10-20 16:17 ` Juri Linkov
2019-10-20 23:54 ` T.V Raman
2019-10-21 21:34 ` Juri Linkov
2019-10-23 16:22 ` Robert Cochran
2019-10-23 20:41 ` Juri Linkov
2019-10-25 15:47 ` Robert Cochran
2019-10-25 16:01 ` Robert Cochran
2019-11-03 22:08 ` Robert Cochran
2019-11-03 22:37 ` Juri Linkov
2019-10-26 21:46 ` Juri Linkov
2019-10-30 18:35 ` Robert Cochran
2019-10-30 21:52 ` Juri Linkov
2019-10-30 23:05 ` Juri Linkov
2019-10-31 1:50 ` Robert Cochran
2019-10-31 21:17 ` Juri Linkov
2019-10-27 23:10 ` 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='CAJ7Ts_3UOvvpsGOJA4_YWn0o8h1eXqONsvaosLqkKLEZet5=bw@mail.gmail.com' \
--to=kalman.reti@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=robert+Emacs@cochranmail.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).