From: martin rudalics <rudalics@gmx.at>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: Tassilo Horn <tassilo@member.fsf.org>,
Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Does display-buffer display the buffer or not?
Date: Fri, 24 Dec 2010 12:49:25 +0100 [thread overview]
Message-ID: <4D1488C5.7040006@gmx.at> (raw)
In-Reply-To: <AANLkTinOybrs7vqU2QJkSdZMp1rxGRoY3m7HbwAGR6Nu@mail.gmail.com>
>> That's a correct conclusion, indeed. The "creating a new frame" part
>> would then have to sidestep `pop-up-frame-function', obviously.
>
> So the average programmers is supposed to know how to handle this, but
> those writing for example the routines that shows a backtrace when
> there is an error are not.
>
> Why is the average programmer better at avoiding looping here?
Emacs doesn't pop up the *Backtrace* buffer by default so the "average"
user is not affected. And the average user is not supposed to customize
`pop-up-frame-function' either. I intended this as a hint for people
writing, for example, a silly `pop-up-frame-function' so they can find
the cuplrit easier. And, obviously, if a function is allowed to return
nil, the doc-string of the function should say so.
martin
next prev parent reply other threads:[~2010-12-24 11:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 5:01 Does display-buffer display the buffer or not? Lennart Borgman
2010-12-24 8:15 ` Tassilo Horn
2010-12-24 9:31 ` martin rudalics
2010-12-24 10:22 ` Tassilo Horn
2010-12-24 11:13 ` martin rudalics
2010-12-24 11:26 ` Lennart Borgman
2010-12-24 11:49 ` martin rudalics [this message]
2010-12-24 12:06 ` Lennart Borgman
2010-12-24 14:41 ` martin rudalics
2010-12-24 15:43 ` Lennart Borgman
2010-12-24 17:57 ` martin rudalics
2010-12-24 11:44 ` Eli Zaretskii
2010-12-24 14:50 ` Tassilo Horn
2010-12-24 15:04 ` martin rudalics
2010-12-24 16:14 ` Eli Zaretskii
2010-12-24 9:31 ` martin rudalics
2010-12-24 9:58 ` Lennart Borgman
2010-12-24 10:27 ` martin rudalics
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=4D1488C5.7040006@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=tassilo@member.fsf.org \
/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).