From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 8865@debbugs.gnu.org
Subject: bug#8865: 24.0.50; `display-buffer' does not respect `pop-up-frames'
Date: Fri, 17 Jun 2011 11:31:54 -0700 [thread overview]
Message-ID: <475597D23B844C31AAD37F8F9782FCC4@us.oracle.com> (raw)
In-Reply-To: <jwv8vt0qvrz.fsf-monnier+emacs@gnu.org>
> > My question was about replacing such a test. The common
> > denominator of the intentions behind using such tests is
> > what all of those tests do (have in common): distinguish
> > nil `pop-up-frames' from non-nil. Nothing more.
>
> If that's all you want to do, then "(if pop-up-frames" is (trivially)
> the only answer.
Well, yes, in Emacs 20-23. But if `pop-up-frames' is being deprecated then what
is the _replacement_ for such a test, going forward?
next prev parent reply other threads:[~2011-06-17 18:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 18:14 bug#8865: 24.0.50; `display-buffer' does not respect `pop-up-frames' Drew Adams
2011-06-14 19:08 ` martin rudalics
2011-06-14 19:43 ` Drew Adams
2011-06-15 9:24 ` martin rudalics
2011-06-15 16:14 ` Drew Adams
2011-06-15 16:26 ` martin rudalics
2011-06-15 17:11 ` Drew Adams
2011-06-15 17:44 ` martin rudalics
2011-06-15 17:53 ` Drew Adams
2011-06-15 22:15 ` Drew Adams
2011-06-16 13:01 ` martin rudalics
2011-06-16 14:01 ` Drew Adams
2011-06-16 15:08 ` martin rudalics
2011-06-16 16:03 ` Drew Adams
2011-06-17 15:46 ` martin rudalics
2011-06-17 18:31 ` Drew Adams
2011-06-19 17:43 ` Drew Adams
2011-06-19 18:50 ` martin rudalics
2011-06-19 20:13 ` Drew Adams
2011-06-16 13:09 ` Stefan Monnier
2011-06-16 14:02 ` Drew Adams
2011-06-17 2:44 ` Stefan Monnier
2011-06-17 15:08 ` Drew Adams
2011-06-17 16:21 ` Stefan Monnier
2011-06-17 18:31 ` Drew Adams [this message]
2011-06-17 21:46 ` Stefan Monnier
2011-06-17 23:55 ` Drew Adams
2011-06-18 1:51 ` Stefan Monnier
2011-06-16 8:45 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=475597D23B844C31AAD37F8F9782FCC4@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=8865@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.