From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id EK++IkRV8GahVQEA62LTzQ:P1 (envelope-from ) for ; Sun, 22 Sep 2024 17:35:00 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id EK++IkRV8GahVQEA62LTzQ (envelope-from ) for ; Sun, 22 Sep 2024 19:35:00 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=gp84Xv6H; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1727026500; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=a2tfKwQxKh6qEJAVXcDSqFcrvIB4EmyfeazVhXqSao0=; b=Wmi7lRz+uLTKeBzFAFDvOaK4nKEPPELc+u9QuSWA4SNB3as+x7QppLFV7XG30FQ7q4u88C TN1l8v5k58TllsIGRAIsKBMCMXR6lVt7M1J1VjlTR0entvaLHcN9f8HbSH/URb+2S+PibZ puIsx+QTAjBVDZqvJzjKYa9mPCNEIY1iIq9uL3WSVy/yqxUWApkdUCMter59xXWqBP02Sy 4QoSnsHoPKRalA+cfAlA4Q+3/Y6o0mE8jhpm7KWGVAeWs/vsH7Ve80AqYlM9k/DQqPeXA9 2muHqI531ymb/kypIXw22PHYGtmCtCPnuqBsqz51fw0hlBhQdCeyY2rZcIbOIA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1727026500; a=rsa-sha256; cv=none; b=ojz5MVePknG+PvuzVkXlLH8ZNmTsE8ye/c6M//NXNz2uOdhdW18/PJvGVd9C7pG2KBy9KH IW/xNKeg05j5pWEcehataUo6ByHNk5zmKcUqjuLbruayf8SDe0RUx+Y7GakbQKBSsrz278 dCdX5Zx08UNvDgfaUKlRnJhIJrIV77X5MjEm0zYsf/e2Ya9/vO7c9oPBKtOnfvrU3hflVU 44rR3Xhe7ChCY8WdAd3uXRmFkYea6/0yfng50AR4uN7iEKnjDW8YMmHdBxODT4XfQvzsp+ +QQeldEmkFiCLe4dijB5q6UVtmX1oHEx0Fiyr6V4+TVI5bCz+lSIifSTkJ9uQA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=gp84Xv6H; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 6169F5FE13 for ; Sun, 22 Sep 2024 19:35:00 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ssQT9-0002qA-PA; Sun, 22 Sep 2024 13:33:59 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ssQT7-0002ph-C5 for emacs-orgmode@gnu.org; Sun, 22 Sep 2024 13:33:58 -0400 Received: from mail-pj1-x1035.google.com ([2607:f8b0:4864:20::1035]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ssQT5-0007NK-Ae for emacs-orgmode@gnu.org; Sun, 22 Sep 2024 13:33:57 -0400 Received: by mail-pj1-x1035.google.com with SMTP id 98e67ed59e1d1-2d86f71353dso2529992a91.2 for ; Sun, 22 Sep 2024 10:33:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727026433; x=1727631233; darn=gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=a2tfKwQxKh6qEJAVXcDSqFcrvIB4EmyfeazVhXqSao0=; b=gp84Xv6Hm1+YA0Mt+Z7Pjoe290mGJ70I/LEZFOrnq15G79sDtkIgxYDfJZVTR6Eo4K 0cfT7H/A+lOjcr4jTmZ1ah3IKiDnlKLAgtrAGzJMWs5UCzQDzm3yANcvD8hm0xdoLZrN AWdFxor7ZZXAk53VwiRtBCDNGrC3/phjGprTRe/KdggC1UbzXzA9JUvSycL6mf0XvuDR wZNqf9MDHtg53nKl7AirbDppDucnQrjZ6lCAdI5UtGLZdAuHBz5ZH3tkQyklVccjokkU nD2vTnAJebF0B7ehRNOTT9gVXb6OiP6xLbsu5MW5GlPJiiO6yVaAjOrNEai1D1ZhYhXB KsmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727026433; x=1727631233; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=a2tfKwQxKh6qEJAVXcDSqFcrvIB4EmyfeazVhXqSao0=; b=HlEDzdF47NHpe8h9juD4d4LI4lbB6Bo+xan0iqxwho6dsQPFDDrEryXyNOgbXxpx4I EMalUZDuupiVkPcVlYCTAq3oPzrVTiYrB/9A7Z8JGkR5cUg6YIMD/Epo4hUTIPAKO8uX blssO37V6lgPKdOIFziyHNI4aUPCRU3oyO++x5hZ5zQiIP0wccheahCxeU82a5yUGabx N+EjJ3MuhUcCjhK7g3orALToNxHOp01ZNxoSCZiWRpbG4TMPoK1z8Cze0fmlmSgr31he fJu97d1MFE0v6r3GOImbDEQ9aGHNEcrgg2TsXDBaWs480xA2YuzYtEb4RmmRuw3Gwe/E PKiQ== X-Gm-Message-State: AOJu0Yzr35nAplEFQ8pRjY8XCY3AnO8Quf5lsOCKWmsJFNSU1OAqzDxY sJ6FsMGF3hXq60Nry2J31vfRXlCa3wSUQH3L901mYslrhWr5GxmqssZoZjvLT0XaZJFEjovIi/I Tw0nybtmFy1f6U8DZ+r/dAeIoiXiT6fuY X-Google-Smtp-Source: AGHT+IEXTPeQBFBgfYUIPdXZbjSVLJ/g7FURJDk+ADAAuw9HoOBX6KJT+jrP6ACfH1QYu7pjqbmSag/LyzZx2kYeVFI= X-Received: by 2002:a17:90b:310b:b0:2d8:f11e:f7e with SMTP id 98e67ed59e1d1-2dd7f3e4f0fmr11713491a91.12.1727026433507; Sun, 22 Sep 2024 10:33:53 -0700 (PDT) MIME-Version: 1.0 References: <87wmjbmmge.fsf@localhost> <87ed5ijeuw.fsf@localhost> <875xqortcj.fsf@localhost> <87ldzjpqox.fsf@localhost> In-Reply-To: <87ldzjpqox.fsf@localhost> From: Amol Vaidya Date: Sun, 22 Sep 2024 12:33:41 -0500 Message-ID: Subject: Re: Org-Capture Window Behavior To: Ihor Radchenko Cc: emacs-orgmode@gnu.org Content-Type: multipart/alternative; boundary="000000000000164abe0622b8ade9" Received-SPF: pass client-ip=2607:f8b0:4864:20::1035; envelope-from=amolvaidya06@gmail.com; helo=mail-pj1-x1035.google.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -5.61 X-Spam-Score: -5.61 X-Migadu-Scanner: mx13.migadu.com X-Migadu-Queue-Id: 6169F5FE13 X-TUID: VanMpSLlO8bK --000000000000164abe0622b8ade9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I'm curious, then, why would what I've done in Test 2 nor corral it? (add-to-list 'display-buffer-alist '("\\*CAPTURE*" (display-buffer-same-window))) On Sun, Sep 22, 2024 at 12:00=E2=80=AFPM Ihor Radchenko wrote: > Amol Vaidya writes: > > > Thank you for your clarification. Just a minor point: my concern is tha= t > > org-capture is not adhering to general display-buffer settings rather > than > > specifically display-buffer-alist. In my case display-buffer-alist is n= il > > when I run emacs -q, but according to section 29.13.1 of the Elisp > manual, > > if display-buffer-alist is nil, then display-buffer should consult the > > display-buffer-base-action user option to decide where to display a > buffer. > > I see. > I think that you misunderstood what `display-buffer-base-action' is for. > It is only used when the Emacs package that is displaying the buffer > does not specify how to display it (in other words, calling > `display-buffer' without specifying ACTION argument) > > That's not what Org capture do. Org capture does tell Emacs how to > display the buffer. Only when the user explicitly overrides Org capture > display settings (via `display-buffer-alist' or > `display-buffer-overriding-action'), the default behavior is changed. > > If you look into the docstring of `display-buffer', you will see that > there are a number of user settings with different priorities: > > display-buffer builds a list of action functions and an action > alist by combining any action functions and alists specified by > display-buffer-overriding-action, display-buffer-alist, the > ACTION argument, display-buffer-base-action, and > display-buffer-fallback-action (in order). Then it calls each > function in the combined function list in turn, passing the > buffer as the first argument and the combined action alist as the > second argument, until one of the functions returns non-nil. > > There is no bug in Org capture that we provide ACTION argument to hint > Emacs using what we believe is a better default compared to generic > buffer popups. > > For you, as a user, the right way to configure how Org capture window is > displayed is customizing `display-buffer-alist'. > > -- > Ihor Radchenko // yantar92, > Org mode contributor, > Learn more about Org mode at . > Support Org development at , > or support my work at > --000000000000164abe0622b8ade9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm curious, then, why would what I've done i= n Test 2 nor corral it?

(add-to-list 'display-buffer= -alist '("\\*CAPTURE*" (display-buffer-same-window)))

On Sun, Sep 22, 2024 at 12:00=E2=80=AFPM Ihor Radchenko <yantar92@posteo.net> wrote:
Amol Vaidya <amolvaidya06@gmail.com&= gt; writes:

> Thank you for your clarification. Just a minor point: my concern is th= at
> org-capture is not adhering to general display-buffer settings rather = than
> specifically display-buffer-alist. In my case display-buffer-alist is = nil
> when I run emacs -q, but according to section 29.13.1 of the Elisp man= ual,
> if display-buffer-alist is nil, then display-buffer should consult the=
> display-buffer-base-action user option to decide where to display a bu= ffer.

I see.
I think that you misunderstood what `display-buffer-base-action' is for= .
It is only used when the Emacs package that is displaying the buffer
does not specify how to display it (in other words, calling
`display-buffer' without specifying ACTION argument)

That's not what Org capture do. Org capture does tell Emacs how to
display the buffer. Only when the user explicitly overrides Org capture
display settings (via `display-buffer-alist' or
`display-buffer-overriding-action'), the default behavior is changed.
If you look into the docstring of `display-buffer', you will see that there are a number of user settings with different priorities:

=C2=A0 =C2=A0 display-buffer builds a list of action functions and an actio= n
=C2=A0 =C2=A0 alist by combining any action functions and alists specified = by
=C2=A0 =C2=A0 display-buffer-overriding-action, display-buffer-alist, the =C2=A0 =C2=A0 ACTION argument, display-buffer-base-action, and
=C2=A0 =C2=A0 display-buffer-fallback-action (in order).=C2=A0 Then it call= s each
=C2=A0 =C2=A0 function in the combined function list in turn, passing the =C2=A0 =C2=A0 buffer as the first argument and the combined action alist as= the
=C2=A0 =C2=A0 second argument, until one of the functions returns non-nil.<= br>
There is no bug in Org capture that we provide ACTION argument to hint
Emacs using what we believe is a better default compared to generic
buffer popups.

For you, as a user, the right way to configure how Org capture window is displayed is customizing `display-buffer-alist'.

--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,=
or support my work at <https://liberapay.com/yantar92>
--000000000000164abe0622b8ade9--