From: "Thomas Ellmenreich" <t.ellmenreich@proxmox.com>
To: "Thomas Lamprecht" <t.lamprecht@proxmox.com>,
<pve-devel@lists.proxmox.com>
Subject: Re: [PATCH cluster 2/2] fix #5475: configurable window title
Date: Thu, 16 Jul 2026 15:51:25 +0200 [thread overview]
Message-ID: <DK01MA29LFAM.VJ3K9BYIK9F9@proxmox.com> (raw)
In-Reply-To: <3f04e2b9-d39f-4604-b169-c3ae530256af@proxmox.com>
That definitely sounds like the better solution. I'll use 'ui-settings'
and then 'title' as the nested settings.
On Thu Jul 16, 2026 at 2:50 PM CEST, Thomas Lamprecht wrote:
[snip]
> The window term is a bit opaque here in the backend, but can be fine..
>
> Would favor using a format here from the start to make this easier to expand, e.g.
> I could imagine adding support for passing a color that gets rendered in the favicon
> e.g. as circle or corner for some differentiating from that side, or a prefix/suffix
> added to the title. Needs more thought, and we can expand such things later true our
> default-key schema support, but might be nicer to start out already with a format
> now already.
>
> we could do a more general "ui" or "ui-settings" one to see this from a global UI
> settings POV? and then there simply "title" or as property.
[snip]
next prev parent reply other threads:[~2026-07-16 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 8:48 [PATCH cluster/manager 0/2] Configurable window titles for nodes Thomas Ellmenreich
2026-07-16 8:48 ` [PATCH manager 1/2] fix #5475: configurable window title Thomas Ellmenreich
2026-07-16 8:48 ` [PATCH cluster 2/2] " Thomas Ellmenreich
2026-07-16 12:50 ` Thomas Lamprecht
2026-07-16 13:51 ` Thomas Ellmenreich [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-03 11:55 [RFC cluster/manager 0/2] Configurable window titles for nodes Thomas Ellmenreich
2026-07-03 11:55 ` [PATCH cluster 2/2] fix #5475: configurable window title Thomas Ellmenreich
2026-07-14 6:43 ` Dominik Csapak
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=DK01MA29LFAM.VJ3K9BYIK9F9@proxmox.com \
--to=t.ellmenreich@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.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.
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.