unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: display-buffer-use-some-frame
Date: Tue, 11 Dec 2018 11:31:19 -0800	[thread overview]
Message-ID: <8636r3g8s8.fsf@stephe-leake.org> (raw)
In-Reply-To: <5BD601F9.2010708@gmx.at> (martin rudalics's message of "Sun, 28 Oct 2018 19:37:45 +0100")

Finally getting back to this.

martin rudalics <rudalics@gmx.at> writes:

> - The first sentence of the doc-string doesn't fit on a whole line.
>
> - The line
>
>          (window (and frame (get-lru-window frame nil (cdr (assq 'inhibit-same-window alist))))))
>
>   is too long.

I see you've fixed these, thanks.

> - In the call
>
>           (window--display-buffer
>            buffer window 'frame alist display-buffer-mark-dedicated)
>
>   you should write 'reuse instead of 'frame.  The latter means that a
>   new frame has been made but you just reuse an existing window.  I
>   noticed this because I made the same error in (an undocumented part
>   of) 'display-buffer-in-child-frame'.

I'll fix this after the test below.

> Also, I wonder why you call
> 'frame-first-window' here:
>
>                            (not (window-dedicated-p
>                                  (or
>                                   (get-lru-window frame)
>                                   (frame-first-window frame)))))

I don't remember. I'll test for a while without it.

-- 
-- Stephe



  reply	other threads:[~2018-12-11 19:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-28 18:37 display-buffer-use-some-frame martin rudalics
2018-12-11 19:31 ` Stephen Leake [this message]
2018-12-12  8:31   ` display-buffer-use-some-frame martin rudalics
2018-12-23 18:23   ` display-buffer-use-some-frame Stephen Leake
2018-12-23 19:07     ` display-buffer-use-some-frame martin rudalics
2018-12-23 22:19     ` display-buffer-use-some-frame Stefan Monnier
2018-12-24  8:13       ` display-buffer-use-some-frame martin rudalics
2018-12-24 13:53         ` display-buffer-use-some-frame Stefan Monnier

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=8636r3g8s8.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=emacs-devel@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).