From: "Drew Adams" <drew.adams@oracle.com>
To: "'martin rudalics'" <rudalics@gmx.at>
Cc: 8865@debbugs.gnu.org
Subject: bug#8865: 24.0.50; `display-buffer' does not respect `pop-up-frames'
Date: Sun, 19 Jun 2011 10:43:35 -0700 [thread overview]
Message-ID: <E117C90C43A54B01BDDC2DC9388834CB@us.oracle.com> (raw)
In-Reply-To: <C5CC47C5DD3441249BC937D99CB3C37C@us.oracle.com>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
FYI - This bug is fixed by the second version of window that you sent me today,
Martin.
To see that it is fixed, load the attached file after emacs -Q, then do this
(same recipe as originally):
M-x find-library-other-window RET frame.el RET
Buffer frame.el is now shown in a separate frame, not just a separate window as
before your latest window.el.
(P.S. The attached file assumes your latest window.el is in the current
directory and named "window-2011-06-19a-MARTIN.el".)
[-- Attachment #2: throw-8865.el --]
[-- Type: application/octet-stream, Size: 958 bytes --]
; emacs -Q
(setq pop-up-frames t)
(require 'find-func)
(load-file "window-2011-06-19a-MARTIN.el")
(defun find-library-other-window (library)
"Find the Emacs-Lisp source of LIBRARY in another window."
(interactive
(let* ((path (cons (or find-function-source-path load-path)
(find-library-suffixes)))
(def (if (eq (function-called-at-point) 'require)
(save-excursion (backward-up-list)
(forward-char)
(backward-sexp -2)
(thing-at-point 'symbol))
(thing-at-point 'symbol))))
(when def (setq def (and (locate-file-completion def path 'test) def)))
(list (completing-read "Library name: " 'locate-file-completion
path nil nil nil def))))
(let ((buf (find-file-noselect (find-library-name library))))
(pop-to-buffer buf 'other-window)))
; M-x find-library-other-window RET frame.el RET
next prev parent reply other threads:[~2011-06-19 17:43 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 [this message]
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
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
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=E117C90C43A54B01BDDC2DC9388834CB@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=8865@debbugs.gnu.org \
--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).