From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jeff Norden Newsgroups: gmane.emacs.bugs Subject: bug#63956: 29.0.91; tex-mode display problem in emacs-29 Date: Mon, 12 Jun 2023 11:41:34 -0500 Message-ID: References: <83h6ri2u2i.fsf@gnu.org> <87ttvhkfw7.fsf@gnu.org> <8335313ise.fsf@gnu.org> <87o7lojthj.fsf@gnu.org> <837csb2731.fsf@gnu.org> <837csazff2.fsf@gnu.org> <83ttvexa1n.fsf@gnu.org> <83pm61yigx.fsf@gnu.org> <83legoyk7i.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10289"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 63956@debbugs.gnu.org, sds@gnu.org, Stefan Monnier To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jun 12 18:43:29 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q8kdd-0002X4-67 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 12 Jun 2023 18:43:29 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q8kdN-0003wA-6C; Mon, 12 Jun 2023 12:43:13 -0400 Original-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 1q8kdD-0003uL-Uj for bug-gnu-emacs@gnu.org; Mon, 12 Jun 2023 12:43:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1q8kdC-0000DL-MM for bug-gnu-emacs@gnu.org; Mon, 12 Jun 2023 12:43:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1q8kdB-0000Ey-O7 for bug-gnu-emacs@gnu.org; Mon, 12 Jun 2023 12:43:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Jeff Norden Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 12 Jun 2023 16:43:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63956 X-GNU-PR-Package: emacs Original-Received: via spool by 63956-submit@debbugs.gnu.org id=B63956.1686588133865 (code B ref 63956); Mon, 12 Jun 2023 16:43:01 +0000 Original-Received: (at 63956) by debbugs.gnu.org; 12 Jun 2023 16:42:13 +0000 Original-Received: from localhost ([127.0.0.1]:40433 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q8kcP-0000Dt-Ay for submit@debbugs.gnu.org; Mon, 12 Jun 2023 12:42:13 -0400 Original-Received: from mail-pg1-f177.google.com ([209.85.215.177]:61732) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q8kcJ-0000Db-Bb for 63956@debbugs.gnu.org; Mon, 12 Jun 2023 12:42:11 -0400 Original-Received: by mail-pg1-f177.google.com with SMTP id 41be03b00d2f7-53fb4ee9ba1so2265651a12.3 for <63956@debbugs.gnu.org>; Mon, 12 Jun 2023 09:42:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686588121; x=1689180121; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=TzpxLGr93aGGUQs1VTPndv38oDW/ctZi1ZJFXfZO96A=; b=K7crrfRTDh/inqHUufQRAmcP0Saxna4yrwqWwXPOK7Uzkxs7UhqL01ol6vCyDpDP78 EPaOFvP46Cw/0Zehed43Xm8jO9cpfUX33sLJHWPThvlU/zISh4XJV0Y8SlDAnEqI1ZPh g49ndIbEi61W1vu3fqo0iU0osFEC2fPC9bsqKVhJ0mqtxlREav8t3WJeyDwKrCfTSDk2 6VBh5ziN58aUW7zemayN04yoOfqBLC5FomURcpVLj8UAQGT2LBhgEyc21l8NqU3eF/fg f8NBdYrSo+yVr7/0jYUVvWmjzN4A0kECGW8OPYC0C8XZ5luBDUflfRuYzes0ZgYeOS1W 1N2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686588121; x=1689180121; h=content-transfer-encoding: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=TzpxLGr93aGGUQs1VTPndv38oDW/ctZi1ZJFXfZO96A=; b=h8xQjzvAKBd+cCNQ1eQkwNBVOMNFOkeuh/ehdp7QJuYk4r0rMiOqROtunxJPSmeLDt kF8Np7DK08a5092HH+LgevEenbaAhb3aJLCI30RG0G7MvQJs8mgIGNiNDAZiL2J2706i P7pO7hrGbajPP9xX0e0kn0C/f1PKZxMV+CQF94nSNAjDYlOKUIZ47kCA73Xv7x9Cr207 pXoHM83EJlffDPAcAPX2R2WMT4Ih7iUyrMp4iqoqjKFe1ir4oCubdCo3iSWrMDXdWSww X7p1eok/lg4H4IHM6TBaEp8DasXrbuvf5Xk72hAPtLOBi82hdr9LEIKCASVmbFamDGGg lyWg== X-Gm-Message-State: AC+VfDzorDEczWKRNxZzdMTb22Fbh4u1YEKnqe94WtYZou3M3WIm15OR Cu8yuo1QjuflBIWRDgNZNB95O89bnzBVDkRdgRQ= X-Google-Smtp-Source: ACHHUZ5ZQk7O6IER+FoDgIFsPSPQ9SRdpJYTlm6dRk6kCvUooWAErR4z7ZDmeA3vY0MEbrZNMp4P4bU2oPJ0TA38w5M= X-Received: by 2002:a17:90a:352:b0:25b:f289:c4f3 with SMTP id 18-20020a17090a035200b0025bf289c4f3mr1847171pjf.30.1686588121178; Mon, 12 Jun 2023 09:42:01 -0700 (PDT) In-Reply-To: <83legoyk7i.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:263289 Archived-At: On Mon, Jun 12, 2023 at 6:48=E2=80=AFAM Eli Zaretskii wrote: > OK, thanks. But did you see any difference between doing this the way > Emacs 28 did (without 2nd argument to pop-to-buffer) and the way the > code now does on the emacs-29 branch? IOW, does this scenario produce > reasonable results after my recent changes? The default behavior in emacs-29 is now the same as it was in 28.2, so I don't see any need to make further changes at this point. --- If my (admittedly limited) understanding of display buffer actions is correct, then calling display-buffer or pop-to-buffer with a 'reuse-window' action would only differ from a call without any action if either: (a) display-buffer-base-action has been customized, or (b) the buffer name has been listed in same-window-buffer-names or matches same-window-regexps This assumes that display-buffer-fallback-action has its default value, which it should since it is defined with defconst in window.el: (defconst display-buffer-fallback-action '((display-buffer--maybe-same-window ;FIXME: why isn't this redundant? display-buffer-reuse-window display-buffer--maybe-pop-up-frame-or-window display-buffer-in-previous-window display-buffer-use-some-window ;; If all else fails, pop up a new frame. display-buffer-pop-up-frame)) Perhaps this answers the question in the above code, --maybe-same-window seems to be for backwards compatibility to allow the use of the same-window- variables, which pre-date window actions. Using display-buffer-alist is the recommended way to do things now, and gets first priority. Thanks, -Jeff