[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fri, 2 Oct 2009 10:55:14 -0700
> >> 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 fucked
> >> 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 BUFFER-OR-NAME argument must be treated consistently through all
> functions that have it. So raising an error is obviously TRT here.
I guess you're right about that.
I was thinking that there might be some functions that did not raise an error
for a non-string, non-buffer, but it seems they all ultimately call
`get-buffer', which chokes if not a string or a buffer.
Re: delete-windows-on, martin rudalics, 2009/10/02