From: "Drew Adams" <drew.adams@oracle.com>
To: "'martin rudalics'" <rudalics@gmx.at>,
"'Juanma Barranquero'" <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: RE: delete-windows-on
Date: Fri, 2 Oct 2009 10:55:14 -0700 [thread overview]
Message-ID: <47CD9C0ADBDC44CDA748F4978DF90DFE@us.oracle.com> (raw)
In-Reply-To: <4AC637A3.3070305@gmx.at>
> >> 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.
next prev parent reply other threads:[~2009-10-02 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 16:16 delete-windows-on Drew Adams
2009-10-02 16:30 ` delete-windows-on Juanma Barranquero
2009-10-02 16:47 ` delete-windows-on Drew Adams
2009-10-02 16:51 ` delete-windows-on Juanma Barranquero
2009-10-02 17:25 ` delete-windows-on martin rudalics
2009-10-02 17:55 ` Drew Adams [this message]
2009-10-02 20:31 ` delete-windows-on Drew Adams
2009-10-03 5:52 ` delete-windows-on Stephen J. Turnbull
2009-10-02 17:37 ` delete-windows-on Drew Adams
2009-10-02 18:27 ` delete-windows-on Stephen J. Turnbull
2009-10-02 17:25 ` delete-windows-on martin rudalics
2009-10-02 17:39 ` delete-windows-on Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47CD9C0ADBDC44CDA748F4978DF90DFE@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).