bug#57890: 28.1; Doc string of `initial-frame-alist'

[Drew Adams]

The doc string seems to suggest that the option, or its use, somehow
depends on X resources:

... If you want the initial frame
to have the proper geometry as soon as it appears, you need to
use this three-step process:
* Specify X resources to give the geometry you want.
* Set 'default-frame-alist' to override these options so that they
  don't affect subsequent frames.
* Set 'initial-frame-alist' in a way that matches the X resources,
  to override what you put in 'default-frame-alist'.

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.

The coverage in the Emacs and Elisp manuals seems OK - doesn't present
this problem/confusion.


In GNU Emacs 28.1 (build 2, x86_64-w64-mingw32)
 of 2022-04-21 built on AVALON
Windowing system distributor 'Microsoft Corp.', version 10.0.19044
System Description: Microsoft Windows 10 Pro (v10.0.2009.19044.1889)

Configured using:
 'configure --with-modules --without-dbus --with-native-compilation
 --without-compress-install CFLAGS=-O2'

Configured features:
ACL GIF GMP GNUTLS HARFBUZZ JPEG JSON LCMS2 LIBXML2 MODULES NATIVE_COMP
NOTIFY W32NOTIFY PDUMPER PNG RSVG SOUND THREADS TIFF TOOLKIT_SCROLL_BARS
XPM ZLIB

(NATIVE_COMP present but libgccjit not available)

Important settings:
  value of $LANG: ENU
  locale-coding-system: cp1252