all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Drew Adams <drew.adams@oracle.com>,  emacs-devel@gnu.org
Subject: Re: [External] : Pop-up-windows vs display-buffer-take-action
Date: Wed, 15 Feb 2023 12:49:14 -0800	[thread overview]
Message-ID: <p91zg9ewt6d.fsf@google.com> (raw)
In-Reply-To: <835yc2advi.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 15 Feb 2023 22:10:41 +0200")

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 774 bytes --]

Given what you say, it would be useful to users if we trimmed the doc
string of  pop-up-windows which presently reads:

pop-up-windows is a variable defined in window.el.

Its value is nil
Original value was t

Non-nil means display-buffer should make a new window.
This variable is provided mainly for backward compatibility and
should not be used in new code.  To make display-buffer behave
as if this were t, customize display-buffer-base-action
instead.  See Info node (elisp) Choosing Window Options in the
Emacs Lisp manual for an example.
Drop everything except the first sentence would be my recommendation.

  You can customize this variable.

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8



  reply	other threads:[~2023-02-15 20:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 15:26 Pop-up-windows vs display-buffer-take-action T.V Raman
2023-02-15 16:46 ` [External] : " Drew Adams
2023-02-15 17:20   ` Eli Zaretskii
2023-02-15 17:38     ` Drew Adams
2023-02-15 18:07       ` Eli Zaretskii
2023-02-15 20:00         ` Drew Adams
2023-02-15 20:10           ` Eli Zaretskii
2023-02-15 20:49             ` T.V Raman [this message]
2023-02-16  7:37               ` Eli Zaretskii

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=p91zg9ewt6d.fsf@google.com \
    --to=raman@google.com \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.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 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.