unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Bading <tbading@web.de>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: icon-title-format vs. frame-title-format (Bug#61496)
Date: Thu, 4 May 2023 06:59:46 +0200	[thread overview]
Message-ID: <550a8411-be93-1cb2-ff55-093c7f03547b@web.de> (raw)
In-Reply-To: <4d6dfc8a-05af-fe07-7e02-b38cd4662e6a@web.de>

> With another not-my-first-language warning, how about this?

Sorry, with ` and ' of course, so something like:

$ git diff -U6 src/xdisp.c
diff --git a/src/xdisp.c b/src/xdisp.c
index 4384754439..6b2290b8e0 100644
--- a/src/xdisp.c
+++ b/src/xdisp.c
@@ -36610,13 +36610,15 @@ syms_of_xdisp (void)
   DEFVAR_LISP ("frame-title-format", Vframe_title_format,
     doc: /* Template for displaying the title bar of visible frames.
 \(Assuming the window manager supports this feature.)
 
 This variable has the same structure as `mode-line-format', except that
 the %c, %C, and %l constructs are ignored.  It is used only on frames for
-which no explicit name has been set (see `modify-frame-parameters').  */);
+which no explicit name has been set (see `modify-frame-parameters').
+
+A similar template for iconified frames may be defined by `icon-title-format'.  */);
 
   DEFVAR_LISP ("icon-title-format", Vicon_title_format,
     doc: /* Template for displaying the title bar of an iconified frame.
 \(Assuming the window manager supports this feature.)
 If the value is a string, it should have the same structure
 as `mode-line-format' (which see), and is used only on frames




  reply	other threads:[~2023-05-04  4:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 18:40 icon-title-format vs. frame-title-format (Bug#61496) Tobias Bading
2023-05-03 18:56 ` Eli Zaretskii
2023-05-03 19:10   ` Tobias Bading
2023-05-04  0:12 ` Po Lu
2023-05-04  4:03   ` Tobias Bading
2023-05-04  4:38     ` Po Lu
2023-05-04  4:46       ` Tobias Bading
2023-05-04  4:59         ` Tobias Bading [this message]
2023-05-04 14:51       ` Óscar Fuentes
2023-05-04 16:08         ` Eli Zaretskii
2023-05-04 16:37           ` Óscar Fuentes
2023-05-04 17:36             ` Eli Zaretskii
2023-05-05  0:15         ` Po Lu
2023-05-05  1:02           ` Óscar Fuentes
2023-05-05  4:44             ` tomas
2023-05-05  5:33               ` Eli Zaretskii
2023-05-05  7:28                 ` tomas
2023-05-05 10:39                   ` Eli Zaretskii
2023-05-05  5:24             ` Po Lu
2023-05-05  5:29           ` Eli Zaretskii
2023-05-05 10:40 ` Tobias Bading
2023-05-05 11:00   ` Eli Zaretskii
2023-05-05 11:00   ` Po Lu
2023-05-05 11:17     ` Eli Zaretskii
2023-05-05 12:29       ` Po Lu
2023-05-05 13:31         ` Eli Zaretskii
2023-05-05 23:52           ` Po Lu
2023-05-06  6:27             ` Eli Zaretskii

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=550a8411-be93-1cb2-ff55-093c7f03547b@web.de \
    --to=tbading@web.de \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.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).