Re: 21.2 Out of sync: window-minibuffer-p arg is optional in Emacs
posting-list(a)mailandnews.com (Jari Aalto+mail.emacs) writes:
This is just my opinion, but if function starts with argument BUFFER
ot WINDOW or FRAME, they all should be optional and by default refer
to current (active) unit.
An argument should be optional only if it makes sense for it to be
optional. For instance, functions used in loops like
`window-next-child' or `window-parent' almost never want to deal with
selected window. Also, doesn't add much value for `window-live-p' to
default to selected window, since the selected window will always be
live.
I'll update window-minibuffer-p for the sake of compatibility, but I
won't touch other functions.