unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: display-buffer-other-frame - useful? doc string?
Date: Mon, 10 Mar 2008 02:11:48 -0400	[thread overview]
Message-ID: <E1JYbEi-00076Z-4i@fencepost.gnu.org> (raw)
In-Reply-To: <002401c8820f$7d6042c0$0600a8c0@us.oracle.com> (drew.adams@oracle.com)

    Is the command `display-buffer-other-frame' useful as it is currently
    designed? It displays a buffer in another frame, but it also lowers
    that frame among all window-manager windows. Even if the buffer was
    already displayed in another frame, that frame is still lowered behind
    all others.

It is certainly wrong to lower the frame.  I wonder why that happens.
Is there explicit code to do it, or is it an unwanted side effect?




  parent reply	other threads:[~2008-03-10  6:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-09 18:00 display-buffer-other-frame - useful? doc string? Drew Adams
2008-03-09 21:48 ` Stefan Monnier
2008-03-09 22:06   ` Drew Adams
2008-03-10 17:16     ` Richard Stallman
2008-03-10 17:19       ` Drew Adams
2008-03-10 17:59       ` Stefan Monnier
2008-03-11 20:24         ` Richard Stallman
2008-03-10 17:15   ` Richard Stallman
2008-03-10 17:34   ` Andreas Schwab
2008-03-10 18:01     ` Stefan Monnier
2008-03-10 18:43       ` Andreas Schwab
2008-03-10  6:11 ` Richard Stallman [this message]
2008-03-10  6:22   ` Drew Adams
2008-04-06  0:13 ` Drew Adams
2008-04-06  2:28   ` Stefan Monnier
2008-04-06  7:52     ` Drew Adams
2008-04-07  0:51       ` Stefan Monnier
2008-04-07  1:18         ` Drew Adams
2008-04-07 16:01           ` Stefan Monnier
2008-04-07 16:14             ` Drew Adams
2008-04-07 16:44               ` Lennart Borgman (gmail)
2008-04-07 16:52                 ` Drew Adams
2008-04-07 17:02                   ` Lennart Borgman (gmail)
2008-04-07 17:06                     ` 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=E1JYbEi-00076Z-4i@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-pretest-bug@gnu.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).