Subject: bug#68081: 30.0.50; derived-mode and display-buffer-alist

From: Eli Zaretskii <[email-masked]>
Date: Thu, 04 Jan 2024 12:39:33 +0200

> Date: Thu, 4 Jan 2024 11:21:17 +0100
> Cc: [email-masked], [email-masked]
> From: martin rudalics <[email-masked]>
> 
>  >> 'info' initially used 'switch-to-buffer'
>  >>
>  >>       (if (get-buffer "*info*")
>  >> 	(switch-to-buffer "*info*")
>  >>         (Info-directory))))
>  >>
>  >> Later it called 'pop-to-buffer' as
>  >>
>  >>       (if (get-buffer "*info*")
>  >> 	(pop-to-buffer "*info*")
>  >>         (Info-directory))))
>  >>
>  >> The breakage occurred when it started to call
>  >>
>  >>     (pop-to-buffer "*info*")
>  >>
>  >> without checking whether that buffer exists.  It sometimes backfires to
>  >> use a feature meant for interactive use (like 'pop-to-buffer' creating
>  >> its buffer autonomously) in non-interactive calls.  Sometimes it happens
>  >> decades after that feature was misused.
>  >
>  > Do other places that are affected by the same change do the same
>  > mistake of unconditionally calling pop-to-buffer?
> 
> Maybe my formulation was not clear.  Basically, all calls of 'info'
> without first argument are affected by the change.

Thanks, but I was asking about callers of pop-to-buffer other than
'info'.  German said in
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=68081#26 that other
callers, in addition to 'info' are also affected.