all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: meedstrom--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "martin rudalics" <rudalics@gmx.at>, 50518@debbugs.gnu.org
Subject: bug#50518: Minor doc bug: pop-up-frames
Date: Sat, 11 Sep 2021 17:50:53 +0000	[thread overview]
Message-ID: <1c45e10ee6aeed0af13f978c8f1b605b@teknik.io> (raw)
In-Reply-To: <3555767c-f574-2781-18f6-528e19300d85@gmx.at>

I understand, don't mark it obsolete, but the docstring should say something about not using it in new code.

September 11, 2021 4:43 PM, "martin rudalics" <rudalics@gmx.at> wrote:

>> The variable pop-up-frames is not marked obsolete nor does the
> 
>> docstring say it exists for backward compatibility -- only the
>> Info manual says it. As a result, it's an unnecessary confusing
>> factor while you are exploring the display-buffer machinery.
> 
> `pop-up-frames' is semi-obsolete. Making it obsolete would give too
> many warnings - it's way too often used in our code base.
> 
> The Info manual says that "This variable is provided mainly for backward
> compatibility." It should not be used in new code because there is no
> guarantee that it will work - newer functions might not pay attention to
> it.
> 
> martin






  parent reply	other threads:[~2021-09-11 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-11 14:15 bug#50518: Minor doc bug: pop-up-frames meedstrom--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-11 16:43 ` martin rudalics
2021-09-11 17:50 ` meedstrom--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-09-12  9:19   ` martin rudalics
     [not found]   ` <9c69aa21f67b3bda7276d6a1e3fc40f4@teknik.io>
2021-09-13  8:01     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1c45e10ee6aeed0af13f978c8f1b605b@teknik.io \
    --to=bug-gnu-emacs@gnu.org \
    --cc=50518@debbugs.gnu.org \
    --cc=meedstrom@teknik.io \
    --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 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.