all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: sds@gnu.org
Cc: 63956@debbugs.gnu.org
Subject: bug#63956: 29.0.91; tex-mode display problem in emacs-29
Date: Thu, 08 Jun 2023 21:34:09 +0300	[thread overview]
Message-ID: <8335313ise.fsf@gnu.org> (raw)
In-Reply-To: <87ttvhkfw7.fsf@gnu.org> (message from Sam Steingold on Thu, 08 Jun 2023 13:44:40 -0400)

> From: Sam Steingold <sds@gnu.org>
> Date: Thu, 08 Jun 2023 13:44:40 -0400
> Posted-To: gmane.emacs.bugs
> 
> > Adding Sam, who made these changes in tex-mode.el.
> 
> Eli, you sent your message to the amazon.com address. Why?

Because that's what appears in Git:

  commit 18b680cfd177e877991be2bd70ead628bbdc0aa0
  Author:     Sam Steingold <sdsg@amazon.com>
  AuthorDate: Tue Dec 28 17:27:41 2021 -0500
  Commit:     Sam Steingold <sdsg@amazon.com>
  CommitDate: Tue Dec 28 17:28:49 2021 -0500

      Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action'

      * lisp/window.el (display-comint-buffer-action): New `defcustom`,
      defaults to 'display-buffer-same-window' for backward compatibility.
      * lisp/cmuscheme.el (run-scheme, switch-to-scheme): Pass
      'display-comint-buffer-action' to 'pop-to-buffer' instead
      of using 'pop-to-buffer-same-window'.
      * lisp/eshell/eshell.el (eshell): Likewise.
      * lisp/shell.el (shell): Likewise.
      * lisp/org/ol-eshell.el (org-eshell-open): Likewise.
      * lisp/progmodes/inf-lisp.el (inferior-lisp): Likewise.
      * lisp/progmodes/project.el (project-shell, project-eshell): Likewise.
      * lisp/textmodes/tex-mode.el (tex-display-shell, tex-compile-default)
      (tex-recenter-output-buffer): Pass 'display-comint-buffer-action'
      to 'pop-to-buffer'.

> The commit is tagged with my correct gnu.org address.

It isn't see above.

> Please only use sds@gnu.org for all communications.

Sorry, I cannot afford proofreading every address I copy from the Git
logs.  I simply don't have that kind of time.

> >  Sam, any comments?
> 
> I do not use `tex-buffer', but C-c C-f (which runs the command
> `tex-file') does exactly what it should - creates a new window showing
> `*tex-shell*'. Moreover, I just tried C-c C-b (which runs the command
> `tex-buffer') and it created a new `*tex-shell*' window too (or re-used
> an existing one) without replacing the window that shows my LaTeX.
> 
> When I made the change, I was trying to fix
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52467 (re-use the existing
> `*tex-shell*' window) and I think I did.
> 
> Jeff, could you please reproduce the issue in `emacs -Q`?

I tried "M-x tex-buffer RET" in "emacs -Q", and I see what Jeff
reports.  Are you sure you don't have any customizations that get in
the way?  Or maybe post the exact sequence of commands you tried?





  reply	other threads:[~2023-06-08 18:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 17:52 bug#63956: 29.0.91; tex-mode display problem in emacs-29 Jeff Norden
2023-06-08  9:15 ` Eli Zaretskii
2023-06-08 17:44   ` Sam Steingold
2023-06-08 18:34     ` Eli Zaretskii [this message]
2023-06-09 20:00       ` Sam Steingold
2023-06-10  5:56         ` Eli Zaretskii
2023-06-10 12:55           ` Gregory Heytings
2023-06-10 13:12             ` Eli Zaretskii
2023-06-10 13:20               ` Gregory Heytings
2023-06-11  6:22           ` Eli Zaretskii
2023-06-11 15:44             ` Jeff Norden
2023-06-11 16:01               ` Eli Zaretskii
2023-06-11 17:31                 ` Jeff Norden
2023-06-11 18:14                   ` Eli Zaretskii
2023-06-11 20:12                     ` Jeff Norden
2023-06-12 11:49                       ` Eli Zaretskii
2023-06-12 16:41                         ` Jeff Norden
2023-06-12 16:44                           ` Eli Zaretskii
2023-06-13  1:34                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-13 11:12                       ` Eli Zaretskii
2023-06-09 16:30   ` Jeff Norden

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=8335313ise.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63956@debbugs.gnu.org \
    --cc=sds@gnu.org \
    /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.