From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Konrad Podczeck Newsgroups: gmane.emacs.bugs Subject: bug#37840: Missing in the Emacs manuals: Date: Mon, 4 Nov 2019 12:20:11 +0100 Message-ID: References: <5440997d-8f3f-12f9-ae9e-c0caadde4a01@gmx.at> <81790531-20E9-4919-A485-0D8FE6F60CE1@univie.ac.at> <38fdbe2c-5f1a-3b37-da5f-e2fa6411d8e1@gmx.at> <4ee75419-6f22-4928-3ddb-1add957fb9e4@gmx.at> <568AD058-07B1-4C58-81C5-32E2492C1EC5@univie.ac.at> <554177EF-4600-4F68-89F1-3AF67A551F65@univie.ac.at> <438c4dfa-f7c2-5f5e-32bc-eafdd7c33cb7@gmx.at> Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Content-Type: multipart/alternative; boundary="Apple-Mail=_D910E2A6-97AF-49AC-A154-A98E57399E81" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="45684"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 37840@debbugs.gnu.org To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Nov 04 12:21:13 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iRaQ3-000Bkd-O2 for geb-bug-gnu-emacs@m.gmane.org; Mon, 04 Nov 2019 12:21:11 +0100 Original-Received: from localhost ([::1]:59666 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iRaQ2-00066q-FA for geb-bug-gnu-emacs@m.gmane.org; Mon, 04 Nov 2019 06:21:10 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60288) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iRaPv-00066g-V8 for bug-gnu-emacs@gnu.org; Mon, 04 Nov 2019 06:21:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iRaPu-0005mT-Gy for bug-gnu-emacs@gnu.org; Mon, 04 Nov 2019 06:21:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:55324) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iRaPu-0005mO-DI for bug-gnu-emacs@gnu.org; Mon, 04 Nov 2019 06:21:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iRaPu-0005g8-4o for bug-gnu-emacs@gnu.org; Mon, 04 Nov 2019 06:21:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Konrad Podczeck Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 04 Nov 2019 11:21:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 37840 X-GNU-PR-Package: emacs Original-Received: via spool by 37840-submit@debbugs.gnu.org id=B37840.157286642321740 (code B ref 37840); Mon, 04 Nov 2019 11:21:02 +0000 Original-Received: (at 37840) by debbugs.gnu.org; 4 Nov 2019 11:20:23 +0000 Original-Received: from localhost ([127.0.0.1]:35911 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iRaPG-0005eZ-Kh for submit@debbugs.gnu.org; Mon, 04 Nov 2019 06:20:23 -0500 Original-Received: from grace.univie.ac.at ([131.130.3.115]:57254) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iRaPD-0005eO-5O for 37840@debbugs.gnu.org; Mon, 04 Nov 2019 06:20:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=univie.ac.at; s=rev2; h=References:To:Cc:In-Reply-To:Date:Subject: Mime-Version:Content-Type:Message-Id:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=MAaF0mz55bclCnIb7rWDJyMerogp914g84Vq4vZzK38=; b=qyy8n3WBiaz6VD+DsxS2fN/AR koJvtnb08PIPV1dq0s95T24go6lBSa2otY8ltSXDrrGr95NwoEhy8fnJ6SJfuGb6KVeGw4RZf1gzb xt9Br6K8bQTPJhMZiE+6F2lRIs2tsb/hCO4j71iC0dqNCzHPfLKlAQyptSDvEdSYiy7vM=; Original-Received: from jarvis.univie.ac.at ([131.130.3.112] helo=jarvis.univie.ac.at) by grace.univie.ac.at with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92.2) (envelope-from ) id 1iRaPB-0001Lk-4B; Mon, 04 Nov 2019 12:20:17 +0100 Original-Received: from 217-149-173-1.nat.highway.telekom.at ([217.149.173.1] helo=[10.0.0.13]) by jarvis.univie.ac.at with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.2) (envelope-from ) id 1iRaPA-0007gx-RB; Mon, 04 Nov 2019 12:20:17 +0100 In-Reply-To: <438c4dfa-f7c2-5f5e-32bc-eafdd7c33cb7@gmx.at> X-Mailer: Apple Mail (2.3601.0.10) X-Univie-Virus-Scan: scanned by ClamAV on jarvis.univie.ac.at X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:170925 Archived-At: --Apple-Mail=_D910E2A6-97AF-49AC-A154-A98E57399E81 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > Am 04.11.2019 um 10:06 schrieb martin rudalics : >=20 > > Suppose, without any display-buffer-alist customization, I have just > > > > (setq display-buffer-base-action > > (quote ( > > (display-buffer-reuse-window display-buffer-pop-up-frame) > > (reusable-frames . x) > > ))) > > > > in my init file, where x can be any of 0,1, nil, visible, all these > > choices don=E2=80=99t matter for this: If I open Emacs, the initial = frame > > shows up, and any file loaded via recent-files, or by dragging on > > the Emacs icon, or by clicking on the file icon, shows up in the > > initial frame, contrary to what is advertised in the > > manual. >=20 > What _is_ advertised in the manual? To quote from Section 28.13.5: Let's consider a user who, as a rule, prefers to display buffers on = another frame. Such a user might provide the following customization: (customize-set-variable 'display-buffer-base-action '((display-buffer-reuse-window display-buffer-pop-up-frame) (reusable-frames . 0))) This setting will cause display-buffer to first try to find a window = showing the buffer on a visible or iconified frame and, if no such frame = exists, pop up a new frame. The words =E2=80=9Canother=E2=80=9D and =E2=80=9Cnew=E2=80=9D suggest = a behavior different from what I described above. >=20 > > However, once a file is loaded, then re-selecting it via > > Menu->Buffers, pops it up in a new frame (with properties as > > specified in defaults-frame-alist). So, what is the relation between > > "display-buffer-base-action=E2=80=9D and =E2=80=9Cdefault-frame-alist=E2= =80=9D? >=20 > If a new frame is created by 'display-buffer', its parameters are > determined by >=20 > (1) any 'pop-up-frame-parameters' entry found, >=20 > (2) the value of 'pop-up-frame-alist' (if the function specified by > 'pop-up-frame-function' processes it - the default does) and >=20 > (3) the value of 'default-frame-alist'. >=20 > So if you use the 'display-buffer-base-action' specification from the > top, only 'default-frame-alist' will be used because you neither > customized any 'pop-up-frame-parameters' nor 'pop-up-frame-alist' (the > latter should not be used anyway). All based on the assumption that > you have customized 'switch-to-buffer-obey-display-actions' so that > Menu->Buffers indeed tries to pop to the buffer. >=20 > martin >=20 --Apple-Mail=_D910E2A6-97AF-49AC-A154-A98E57399E81 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

Am 04.11.2019 um 10:06 schrieb martin rudalics <rudalics@gmx.at>:

> = Suppose, without any display-buffer-alist customization, I have just
>
> (setq display-buffer-base-action
>         (quote = (
>    (display-buffer-reuse-window = display-buffer-pop-up-frame)
> =    (reusable-frames . x)
> )))
>
> in my init file, where x can be any = of 0,1, nil, visible, all these
> choices don=E2=80=99t = matter for this: If I open Emacs, the initial frame
> = shows up, and any file loaded via recent-files, or by dragging on
> the Emacs icon, or by clicking on the file icon, shows = up in the
> initial frame, contrary to what is = advertised in the
> manual.

What _is_ advertised in the manual?

To = quote from Section 28.13.5:

Let's consider a user = who, as a rule, prefers to display buffers on another frame. Such a user = might provide the following customization:
     (customize-set-variable
      'display-buffer-base-action
      '((display-buffer-reuse-window display-buffer-pop-up-frame)
        (reusable-frames . 0)))

This setting will = cause display-buffer to = first try to find a window showing the buffer on a visible or iconified = frame and, if no such frame exists, pop up a new frame.


The words =  =E2=80=9Canother=E2=80=9D  and =E2=80=9Cnew=E2=80=9D =  suggest a behavior different from what I described = above.



> However, once a file is loaded, then re-selecting it = via
> Menu->Buffers, pops it up in a new frame (with = properties as
> specified in defaults-frame-alist). So, = what is the relation between
> = "display-buffer-base-action=E2=80=9D and =E2=80=9Cdefault-frame-alist=E2=80= =9D?

If a new frame is created by = 'display-buffer', its parameters are
determined by

(1) any 'pop-up-frame-parameters' entry = found,

(2) the value of = 'pop-up-frame-alist' (if the function specified by
=    'pop-up-frame-function' processes it - the default = does) and

(3) the value of = 'default-frame-alist'.

So if you use the = 'display-buffer-base-action' specification from the
top, = only 'default-frame-alist' will be used because you neither
customized any 'pop-up-frame-parameters' nor = 'pop-up-frame-alist' (the
latter should not be used = anyway).  All based on the assumption that
you have = customized 'switch-to-buffer-obey-display-actions' so that
Menu->Buffers indeed tries to pop to the buffer.

martin


= --Apple-Mail=_D910E2A6-97AF-49AC-A154-A98E57399E81--