From: Juri Linkov <juri@linkov.net>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel@gnu.org, Alan Mackenzie <acm@muc.de>
Subject: Re: Deleting functions and variables obsolete since 24.1--24.3
Date: Sun, 21 Aug 2022 19:16:10 +0300 [thread overview]
Message-ID: <86wnb2u1wd.fsf@mail.linkov.net> (raw)
In-Reply-To: <CADwFkmmspxWO6+rjd4d0b45ehVJnRUWQSTj=XnNDz=K4yFi=jg@mail.gmail.com> (Stefan Kangas's message of "Tue, 16 Aug 2022 07:15:28 -0700")
> Please see the scratch/obsolete-24.3 branch. If there are no protests,
> I will push it to master in a month or so.
I noticed this comment in the branch:
diff --git a/lisp/proced.el b/lisp/proced.el
index a27638d367..29e2860fba 100644
--- a/lisp/proced.el
+++ b/lisp/proced.el
@@ -1768,6 +1768,8 @@ proced-with-processes-buffer
(save-window-excursion
;; Analogous to `dired-pop-to-buffer'
;; Don't split window horizontally. (Bug#1806)
+ ;; FIXME: `dired-pop-to-buffer' was removed. Should we just
+ ;; use `pop-to-buffer' here also?
(display-buffer (current-buffer)
'(display-buffer-in-direction
(direction . bottom)
But the obsolesce message in etc/NEWS.24 informs:
** The following functions and variables are obsolete:
*** 'dired-pop-to-buffer' (use 'dired-mark-pop-up')
So the replacement is 'dired-mark-pop-up' rather than `pop-to-buffer'.
next prev parent reply other threads:[~2022-08-21 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 22:11 Deleting functions and variables obsolete since 24.1--24.3 Stefan Kangas
2022-06-30 23:15 ` Stefan Monnier
2022-07-08 11:58 ` Stefan Kangas
2022-07-08 12:29 ` Stefan Kangas
2022-07-08 12:42 ` Eli Zaretskii
2022-07-08 17:14 ` Stefan Kangas
2022-07-10 3:07 ` Richard Stallman
2022-08-16 14:15 ` Stefan Kangas
2022-08-16 14:50 ` Robert Pluim
2022-08-16 16:31 ` [External] : " Drew Adams
2022-08-17 2:13 ` Po Lu
2022-08-21 16:16 ` Juri Linkov [this message]
2022-08-23 3:20 ` Stefan Kangas
2022-09-09 9:48 ` Stefan Kangas
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=86wnb2u1wd.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=stefan@marxist.se \
/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).