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: Sun, 11 Jun 2023 10:44:38 -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> 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="30409"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 63956-done@debbugs.gnu.org, sds@gnu.org, monnier@iro.umontreal.ca To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Jun 11 17:46:21 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 1q8NGn-0007jD-JX for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 11 Jun 2023 17:46:21 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q8NGX-0003aN-QH; Sun, 11 Jun 2023 11:46:05 -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 1q8NGV-0003aA-3t for bug-gnu-emacs@gnu.org; Sun, 11 Jun 2023 11:46:03 -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 1q8NGU-0006pN-EP for bug-gnu-emacs@gnu.org; Sun, 11 Jun 2023 11:46:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1q8NGT-0007Dn-TB for bug-gnu-emacs@gnu.org; Sun, 11 Jun 2023 11:46: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: Sun, 11 Jun 2023 15:46: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-done@debbugs.gnu.org id=D63956.168649831327697 (code D ref 63956); Sun, 11 Jun 2023 15:46:01 +0000 Original-Received: (at 63956-done) by debbugs.gnu.org; 11 Jun 2023 15:45:13 +0000 Original-Received: from localhost ([127.0.0.1]:37621 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q8NFh-0007Cf-Fb for submit@debbugs.gnu.org; Sun, 11 Jun 2023 11:45:13 -0400 Original-Received: from mail-pg1-f181.google.com ([209.85.215.181]:48629) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q8NFe-0007CQ-Rl for 63956-done@debbugs.gnu.org; Sun, 11 Jun 2023 11:45:11 -0400 Original-Received: by mail-pg1-f181.google.com with SMTP id 41be03b00d2f7-51b4ef5378bso2252827a12.1 for <63956-done@debbugs.gnu.org>; Sun, 11 Jun 2023 08:45:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686498305; x=1689090305; 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=BIsXqc5MospOjQEph4bMNcPsye9FbtQ6hEVMNWnloDI=; b=FvGPhDXFfMTKg7qQET6Du+JAzGRhI1KXtZmr5Jml9gwqMgtInfXVcN4fqJYvbEOXCj oNgdQg3d4yL3mFZDY0PvUB8kk9bwwRrw5nJu8ETjtM0LlnsIezI5GE4FVolgRvlgrxtK FUjyJhUvfQhruzLETZ45PnpP4vvWLYP6jzaRC/PhDBkNav4uZpzUSIQFvo9ojw/StA03 t47m/V0m8LMH1Ft53FDYJuNjggyxnMcqLE4Js91vr+DSDQHWqAf6n1LGETQBuSoz2N4c siD2/EvQxQB7c5a4fnOBPfy3xNwf8h2BHL3VGSYuQ4wESV3axlrXyzSQKvRgi+UXr5hm G4+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686498305; x=1689090305; 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=BIsXqc5MospOjQEph4bMNcPsye9FbtQ6hEVMNWnloDI=; b=jgWWoROAMKy50FRzOELwX8T00tFek1XM76yfbUadNEyIsFgSa2+aUlg4VZtxusSrXV koQt3E7LfPHccbarw87yBBS0G2dRVoexgkzNqNyvpdqKaLu8QZpCmscrMLa91XrXe5gz XR+vWXQoI/rmYd6nqT+eUra62p+kmVbMlXUN5TfWsZPHK8SdiXaPlYX80YxAtw8j47MK TTTZy+m5miiY2I6pxRYgOEby2Xf4ZWjeWID4u8L64xx/4Iup3UHRFsr+EKtzcL6/wniF 0/QzpLyda2mxJ2e0KTFrGjsWoe3mICJXmcxETshd1vLqdssJ51zxM50UnKh5ARyBdgbQ r2aA== X-Gm-Message-State: AC+VfDxTaXu2F+GY/iKsWNkdpk++PecSkiO6biN6P6hNXqMKzN1HNH+l bY1xDXNX9O8qrsRddtzFSArXnBO2wJL+loIYgDI= X-Google-Smtp-Source: ACHHUZ4WWjk3X3yCB/ZyDXmh7SlX35ZJTmzBvBnGrtojPxRzZ3etemXLe9nDtMAU/ReX2mASgJhs8DMZ6TWC415IBMw= X-Received: by 2002:a17:90b:1b50:b0:259:dda1:bee1 with SMTP id nv16-20020a17090b1b5000b00259dda1bee1mr6834579pjb.46.1686498304604; Sun, 11 Jun 2023 08:45:04 -0700 (PDT) In-Reply-To: <837csazff2.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:263249 Archived-At: On Sun, Jun 11, 2023 at 1:22=E2=80=AFAM Eli Zaretskii wrote: ... > No further comments, so I've now added a new defcustom, called > display-tex-shell-buffer-action, and made its default value be > display-buffer-in-previous-window. With that, I'm closing this bug. Eli: Sorry for the delay. I started to compose this response yesterday, but life intervened before I could finish and send it. Adding a new defcustom would be fine as well. --------------- I suggest just removing the actions from the two display-buffer calls and the pop-top-buffer call in tex-mode.el. I think this is definitely the right thing for the display-buffer calls, which apply to the *tex-buffer* created by `tex-file', etc. This buffer is very much like a *compilation* buffer. In fact, you can do much the same thing as tex-file using "M-x compile" by just changing "make -k" to "tex foo.tex" in the minibuffer. However, a *tex-shell* window works better for parsing errors, etc, since it is set up for TeX. In compile.el, display-buffer is actually called with an action of: '(nil (allow-no-window . t)) but I have no idea why. I can't think of a reason to run TeX on a file and not display the *tex-shell* buffer. The pop-to-buffer call only applies to a docview buffer created for previewing a pdf. This isn't a comint or shell window of any sort. Opening in a new frame might make sense, but I wouldn't suggest changing the behavior right now. ---- It was interesting to use tex-mode under 'emacs -Q', which I haven't done for many years. I've got a number of ideas for fixes and improvements. I'll try to write them up in a cogent way and post to emacs-devel for discussion. There is certainly nothing urgent enough to consider for the (imminent?) emacs-29 release. --------------- More generally: comint derived modes can be, and are, used for a variety of purposes. It seems that the intention of the new defcustom introduced by Sam is that it should apply to ones that provide an interactive shell-type buffer that is independent of other tasks. I wonder if 'display-shell-buffer-action' might be a better name. In any case, I think it would be good for the defcustom doc-string to list the derived modes that use it, so that people would know just what to expect if they customize it. It might even make sense to eventually use it for things like the pop-to-buffer call in `scratch-buffer', since lisp-interaction is a shell in the general sense. Currently, scratch-buffer uses pop-to-buffer-same-window like shell-mode previously did. Thanks, -Jeff