bug#1724: 23.0.60; fringe appears in spite of specification

["Drew Adams" <drew.adams@oracle.com>]

This is a piece of bug #117, which describes several problems with
frame parameters.

This is the bug that, even when `default-frame-alist' specifies no
fringe, the initial frame has fringe. I'm creating a new bug
report for this small piece of 117, to simplify things.
 
Save the code below to a file named `bug-117-fringe.el", then do this:
 
runemacs.exe -Q --debug-init -l "bug-117-fringe.el" -f "foo"
 
;----------------------------------------------
(defun foo ()
  (setq default-frame-alist
        (append '((minibuffer)
                  (left-fringe . 0)
                  (right-fringe . 0))
                default-frame-alist))
  (setq minibuffer-frame-alist
        (append '((minibuffer . only))
                minibuffer-frame-alist)))
 
(add-hook 'after-make-frame-functions
          (lambda (fr) (set-frame-size fr 60 20)))
;----------------------------------------------
 
This code works in Emacs 20 through 22. In Emacs 23, the first,
non-minibuffer frame has both left and right fringe, in spite of the
value of `default-frame-alist'. Note that without the call to
`set-frame-size' in `after-make-frame-functions' the problem does not
appear.
 
The Elisp manual, node Initial Parameters, says this about
`default-frame-alist':
 
"This is an alist specifying default values of frame parameters for
 all Emacs frames--the first frame, and subsequent frames.  When
 using the X Window System, you can get the same results by means
 of X resources in many cases."
 
NB: "the first frame, and..."
         ^^^^^
 

In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2008-12-19 on LENNART-69DE564
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include
-fno-crossjumping'