RE: Add hook to end of `custom-create-buffer-internal'

[Drew Adams]

1. No, that doesn't fix it for me.

I don't want to get into the details. In any case, this problem is not about
using fit-frame or about special-display buffers. It is about being able to
do something (anything) after the buffer has been filled with its contents.

If you would please move the existing hook call to after the buffer has been
filled, as you originally suggested, that would solve the pb. The pb should
be fixed in custom-buffer-create-internal, so that it affects all custom
functions that open Customize buffers.

2. Looking at the code, I see that the previous bug I filed (email subject
"custom*-other-window cmds don't respect special-display* values") has not
yet been fixed.

Did you decide that it is not a bug, or hasn't anything been decided about
it yet? Here is a snippet from Stefan's reply to my email, to remind you of
the bug:

    > (let ((window (selected-window))
    >         ;; Copied from `custom-buffer-create-other-window'.
    >         (pop-up-windows t)
    >         (special-display-buffer-names nil)
    >         (special-display-regexps nil)
    >         (same-window-buffer-names nil)
    >         (same-window-regexps nil))
    >     (pop-to-buffer name)
    >     (select-window window))

    > To me, this is a bug - setting the special-display* variables to nil
    > short-circuits my attempts to make the
    > customize-*-other-window commands
    > behave as the other customize buffers behave.

    Agreed.  Setting same-window-* to nil is probably OK, but we
    should never mess with special-display-*.

3. The customize-group-other-window code confuses me because it seems to do
some of what custom-buffer-create-other-window does, and then it calls the
latter, which repeats those things (e.g. pop-to-buffer). Is this correct?

Thanks,

   Drew