unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tobias Bading <tbading@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: icon-title-format vs. frame-title-format (Bug#61496)
Date: Fri, 05 May 2023 14:00:11 +0300	[thread overview]
Message-ID: <83pm7fhwlg.fsf@gnu.org> (raw)
In-Reply-To: <4920048a-aded-3588-50d2-4bea3c0c096b@web.de> (message from Tobias Bading on Fri, 5 May 2023 12:40:37 +0200)

> Date: Fri, 5 May 2023 12:40:37 +0200
> From: Tobias Bading <tbading@web.de>
> 
> Oh god, what have I done? XD
> [...]
> What were we talking about again?
> Right, that frame-title-format doc string… XD
> I didn’t intend to start a mega-thread about terminology. If Emacs doc
> strings had see-also sections I would have simply asked to please put a
> “See also: icon-title-format” into frame-title-format’s doc string.
> I’m happy with the added (setq icon-title-format t) in my ~/.emacs, which
> made Emacs 29 behave like Emacs 26.3. I just thought a little hint in the
> doc string might help other people who upgrade their Emacs like me and
> wonder about those changing window titles.

Something to consider when you post a message about some minor (in
this case, really minuscule) issue.  There's a lesson to be learned
here, I think.

Bottom line: from my POV, there's nothing wrong with our doc strings.
icon-title-format has a reference to frame-title-format, and there's a
reason for that.  There's no reason for the reverse reference, so we
don't have it.

Blindly adding a "see also" for every possible subject under the sun
is not something we do, and should not do.  References should be
instrumental, focused, and to the point, otherwise they are just a
distraction and a cause for user frustration.

The manual, OTOH, shows a broader picture, and thus describes both of
them, and provides some context which allows the reader to understand
the logic behind having both.  The right way of using the Emacs
documentation is to start with doc strings (perhaps via apropos
commands), then look in the manual if the issue is still not clear or
if there's a need for deeper, more comprehensive understanding of the
issue and its aspects.

Expecting the doc strings to answer all the questions and include all
the references to all the possible tangents is impractical.



  reply	other threads:[~2023-05-05 11:00 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
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 [this message]
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=83pm7fhwlg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=tbading@web.de \
    /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).