From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Yuri Khan Newsgroups: gmane.emacs.devel Subject: Re: Modernize frame-title-format: "%b - GNU Emacs" Date: Sun, 30 Aug 2020 01:25:36 +0700 Message-ID: References: <86d03bpqsw.fsf@protonmail.com> <4276dbad-f8ed-4a5d-8960-800b4b059a61@default> <8f1fe768-eafe-47b2-ad66-bfc29f895322@default> 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="28258"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Wayne Harris , Emacs developers To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 29 20:26:56 2020 Return-path: Envelope-to: ged-emacs-devel@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 1kC5Z1-0007Di-AV for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Aug 2020 20:26:55 +0200 Original-Received: from localhost ([::1]:58428 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kC5Z0-00038l-Cj for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Aug 2020 14:26:54 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47506) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kC5Xz-0002cy-C9 for emacs-devel@gnu.org; Sat, 29 Aug 2020 14:25:51 -0400 Original-Received: from mail-vs1-xe2e.google.com ([2607:f8b0:4864:20::e2e]:40957) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kC5Xx-0003cm-Au for emacs-devel@gnu.org; Sat, 29 Aug 2020 14:25:51 -0400 Original-Received: by mail-vs1-xe2e.google.com with SMTP id v138so1295551vsv.7 for ; Sat, 29 Aug 2020 11:25:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=WZH7tm4hd1Y/XAhRny7YplcXa/ElZiOhBtSxf0k5AsU=; b=H3DSaAcGlnA2NMc9o1zwHWvCViZkA3X8aG8bk4mOLlBK13diTQwclm0FXPQjYGWoHO b8Kw57p3AtHtL4s2b7gaPjw9mjHiYBtupDrmqH9Y7+VwpWDq8BODw6dj8oLgxtkRuDHQ 6b0YHuJEfyOL7zFky66fDeZU6OZvsiNKfw+wEwWhoePdIkkTopiYIAPHgAAkTvX7zXT1 VKxrRDQmsvrMDtS1PzSiJIfbhdMUTYfOYnG7TzXCIgEf+Tq9MMMDcPKSanNQ9VlJW6dh nf386LaB3aqJq0EKnHFg3fBn+nzUiqmNYTxdTBRb8S17GNHgrtNTjD5O2aZqPMR9+mcg 61KQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=WZH7tm4hd1Y/XAhRny7YplcXa/ElZiOhBtSxf0k5AsU=; b=RIxBOU6j/peCtLhvhLetaSZA5v1szF8nCdYTXl07aGGvMyYDUyPwLtSsXmFtqh1B1t 9/wW9Pj6uClQsVAXlV2wn4exo9bSALbZsohmb9hHBrjpkjN2i0FxdehQKVN7Mbv+myIz mqpaVh40Yv6C8H+nrX94FZGovyVXHxBGrAkAvJVmXWs65eQyiTWMCJ490/jdI88meXvf 7TKDNJTxJzZP0/tHfpbi+Z2ieUlReLiUjVF9YwpHfEJNrnbAna+2l7/sCo7Jg2jHPwxI A64T9C+1CTFT9zF08ASfi7xd3RbTS4/Gj/ClNblck/eJH+sIoXzXtRLGLSIMTKg9Zq8+ 5G+Q== X-Gm-Message-State: AOAM5324t4SQl/pTf9tRTBxN9yPglU/v8j3E7uEB3zbIjwdpEDGeW1vD 9mctodEd/td0YY6GXuipSr94xaaAuxMIXiLMZaY= X-Google-Smtp-Source: ABdhPJzsWRMjp0bIHskmUYAykqj5T09Je3n2EFbAhMDSiMXTaKyIL2Y3gx2g1vNZ9/6UXYtA+6zaezq7ALLeU+wgBwQ= X-Received: by 2002:a67:ed89:: with SMTP id d9mr2125940vsp.97.1598725548306; Sat, 29 Aug 2020 11:25:48 -0700 (PDT) In-Reply-To: <8f1fe768-eafe-47b2-ad66-bfc29f895322@default> Received-SPF: pass client-ip=2607:f8b0:4864:20::e2e; envelope-from=yurivkhan@gmail.com; helo=mail-vs1-xe2e.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:254395 Archived-At: On Sat, 29 Aug 2020 at 23:37, Drew Adams wrote: > Where is this convention defined? Is it a real > "thing" - some standard or something, or is it > just that you've noticed that many apps use such > naming? I'm not challenging you; just curious > about this. Now that I started looking, it seems that only Windows actively recommends putting the application name in the window title. Windows: https://docs.microsoft.com/en-us/windows/win32/uxguide/text-ui | Choose the title bar text based on the type of window: | | *Top-level, document-centric program windows:* | Use a "document name program name" format. | Document names are displayed first to give a document-centric feel. GNOME 2: https://developer.gnome.org/hig-book/unstable/windows-properties.html.en | Use Filename as the window title for document-based applications. | Do not use the full pathname, | as the filename alone is easier to distinguish | amongst other open window titles, | for example on the window list. | | When a document has pending changes, | insert an asterisk (*) at the beginning of the window title. | For example, *Unsaved Drawing, *AnnualReport. | | While document names are most pertinent to users, | we understand that application developers may want | to increase recognition of their application. | If you plan to include your application's name | in the title of a primary window, | use the following format: Document Name - Application Name. | This will ensure | that the document name appears in limited space situations | such as the system window list. | | Including the application name | in the title of a document-based application is not recommended. GNOME 3 HIG is still not fleshed out enough to talk about window titles. macOS: https://developer.apple.com/design/human-interface-guidelines/macos/windows= -and-views/window-anatomy/ | Most title bars display the filename, | although this isn=E2=80=99t always the case. : | For document windows, | the title is the name of the document | or Untitled (for new documents). > > I do not know which browsers and mail clients you use but Firefox and> = > Thunderbird do append =E2=80=9C- Mozilla Firefox=E2=80=9D and =E2=80=9C- = Thunderbird=E2=80=9D to every > > title, at least for me on GNU/Linux, and I remember it being that way > > back when I was using Windows. > > On Windows I don't see it in Firefox, Google Chrome, > IE, or Brave (chromium). > > But I guess I'm not really seeing a frame (wm window) > title. As those browsers all use tabs, it's the tab > title I guess I've been talking about, for a browser. > I don't see a separate window title. And googling > for that suggests that you need to fiddle or use an > add-on to implement or fake a window title. (Is that > correct? It's my impression, so far.) Hey, that=E2=80=99s a whole different kettle of fish. Yes, recently, many applications go out of their way so as not to have a proper title bar when running with a window manager that supports client-side decorations (i.e. lets applications assume responsibility for drawing a title bar). Fortunately, i3 tacks a title bar on them anyway; also fortunately, these applications still have usable title strings for the window manager to display.