all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: 15189@debbugs.gnu.org
Subject: bug#15189: 24.3.50; display-buffer does not work well with custom frames.
Date: Mon, 26 Aug 2013 15:06:48 +0200	[thread overview]
Message-ID: <521B52E8.3050109@gmx.at> (raw)
In-Reply-To: <m2li3pcm1o.wl%esq@lawlist.com>

 > This does not work well with find-file in conjunction with several
 > frames because find-file is executed BEFORE custom frame functions are
 > run.  The result is that the buffer that initially had focus ends up
 > getting buried even though the file being opened is in a new frame.
 > The only reliable workaround appears to be calling the find-file
 > command AFTER the custom frame functions are run, which (in my lay
 > opinion) defeats the purpose of using display-buffer.

IIUC you want to make `find-file' behave like `find-file-other-frame' by
default.  Is that correct?  Or what am I missing?

martin





  reply	other threads:[~2013-08-26 13:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26  0:50 bug#15189: 24.3.50; display-buffer does not work well with custom frames Keith David Bershatsky
2013-08-26 13:06 ` martin rudalics [this message]
     [not found]   ` <4066A3F6-AB96-43EE-B8F4-E3DF2F73CBD2@lawlist.com>
2013-08-26 15:01     ` martin rudalics
     [not found]     ` <521B6B84.5060106@gmx.at>
     [not found]       ` <742F02FA-4469-4BCA-94A5-D8A7A679B52B@lawlist.com>
2013-08-26 16:34         ` martin rudalics
2013-08-26 20:15 ` Keith David Bershatsky
2013-08-27  6:47   ` martin rudalics
2013-08-28  3:59     ` Kevin Rodgers
2013-08-28 16:35     ` Keith David Bershatsky
2013-08-29  0:21     ` Keith David Bershatsky
2013-08-27 22:30 ` Keith David Bershatsky

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=521B52E8.3050109@gmx.at \
    --to=rudalics@gmx.at \
    --cc=15189@debbugs.gnu.org \
    --cc=esq@lawlist.com \
    /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.