RE: customize-*-other-window cmds don't respect special-display* values

[Drew Adams]

        All of the customize commands work correctly, except for
        the *-other-window
        commands. The *-other-window commands do not respect
        special-display-regexps, so I don't get the proper frame,
        as defined by special-display-frame-alist.

    The purpose of ...-other-window commands is to display a certain
    buffer in a particular way.  That overrides other less specific
    instructions about how to display the buffer.

What in the name "-other-window" indicates that the particular way the
function displays the buffer should override those particular settings? What
are the particular instructions included in the "other-window" name/license.

Find-file-other-window doesn't turn on your headlights or open the oven
door, just because it has an "other-window" license.

You make the general argument that because this is an "other-window"
function it has the right to override things. OK ((maybe)). But what things?
Anything? Everything? Just because it's called "other-window"?

What's the reason for these particular side effects? Are they important or
even appropriate for "other-window"ness in general? For this particular
customize-other-window-ness? How so?

 - Drew