unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 57890@debbugs.gnu.org
Subject: bug#57890: 28.1; Doc string of `initial-frame-alist'
Date: Sun, 18 Sep 2022 19:16:06 +0300	[thread overview]
Message-ID: <834jx4zmih.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488EF3CB04191C48463E8BAF34A9@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Sun, 18 Sep 2022 16:08:03 +0000)

> From: Drew Adams <drew.adams@oracle.com>
> CC: "57890@debbugs.gnu.org" <57890@debbugs.gnu.org>
> Date: Sun, 18 Sep 2022 16:08:03 +0000
> 
> > > The doc string seems to suggest that the option, or its use, somehow
> > > depends on X resources:
> > 
> > And it does.  So I don't understand the complaint.
> 
> Complaint?
> 
> It depends on X resources if you have X resources.
> I'm on MS Windows, for example.  Nothing about X
> resources is relevant to `initial-frame-list' on
> that platform, IIUC.

That is incorrect, see the node "MS-Windows Registry" in the Emacs
user manual (the last paragraph thereof).

> > > That text is not introduced by anything saying, e.g., IF you are
> > > using X resources or by saying that this 3-step process is
> > > applicable only if you can use X resources.  At least some of it
> > > doesn't make sense without X resources, AFAIK.
> > 
> > Doc strings are not nodes in a manual, they cannot have introductions
> > and terminology explanations.  They are succinct and assume some level
> > of general knowledge.
> 
> Yes.  And?  This doc string includes platform-specific
> info without saying that's what it is, no?

It assumes that every user knows enough to understand that.


> If you want to make it more succinct, and leave
> out that X resources info, that's also a way to
> remedy the confusion.

Yes.  Another effective method is to close this bug.





  reply	other threads:[~2022-09-18 16:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17 22:22 bug#57890: 28.1; Doc string of `initial-frame-alist' Drew Adams
2022-09-18  5:38 ` Eli Zaretskii
2022-09-18 16:08   ` Drew Adams
2022-09-18 16:16     ` Eli Zaretskii [this message]
2022-09-18 17:05       ` Christopher Dimech
2022-09-18 10:49 ` Lars Ingebrigtsen
2022-09-18 11:11   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-18 11:20     ` Lars Ingebrigtsen
2022-09-18 11:59       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=834jx4zmih.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57890@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).