[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fri, 2 Oct 2009 18:51:54 +0200
On Fri, Oct 2, 2009 at 18:47, Drew Adams <address@hidden> wrote:
> 1. What "default buffer"? No such default is defined/implemented here, AFAICT.
> 2. Besides, it is not the purpose of `delete-windows-on' to determine whether
> the BUFFER arg in fact corresponds to an existing buffer or someone just
> up. Its purpose is to delete a window (or do nothing).
No. Its purpose is to "[d]elete all windows showing BUFFER-OR-NAME."
An incorrect BUFFER-OR-NAME is an error.
> a. What to return, and whether the return value is significant (hence
> documented) or the function is instead called only for its side effect.
In general, I prefer functions that clearly state what do they return,
even if it is always nil.
> b. What to do when BUFFER does not represent a buffer. Raise an error? Do
Raise an error, IMHO.
> Whatever choice is made, the documentation should reflect it.
> Please read the entire mail I sent.
Unnecessary. The fact that I only answer about *one* point of your
message does not mean that I didn't read or understood the rest. It
just means that I was interested in addressing just *one* point of
Re: delete-windows-on, martin rudalics, 2009/10/02