unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sam Steingold <sds@gnu.org>
To: 63956@debbugs.gnu.org
Subject: bug#63956: 29.0.91; tex-mode display problem in emacs-29
Date: Fri, 09 Jun 2023 16:00:56 -0400	[thread overview]
Message-ID: <87o7lojthj.fsf@gnu.org> (raw)
In-Reply-To: <CAPbFCnmaNPxu20=9g+nbc7s2T+Mxt8QU3kN7OMuu+voEwxmwPA@mail.gmail.com>

> * Eli Zaretskii <ryvm@tah.bet> [2023-06-08 21:34:09 +0300]:
>
>> 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'.

here is what I see:

commit 18b680cfd177e877991be2bd70ead628bbdc0aa0
Author: Sam Steingold <sds@gnu.org>
Date:   2021-12-28 17:27:41 -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.

I am confused.

>> 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.

I am with you, but note that you risk getting your emails bouncing.

> Are you sure you don't have any customizations that get in the way?

Yeah, looks like I do:
--8<---------------cut here---------------start------------->8---
 '(display-buffer-alist
   '(("shell\\*" nil (inhibit-same-window . t))))
--8<---------------cut here---------------end--------------->8---

When my change was discussed, I was told that adding a new custom
variable was okay, but making it have non-trivial default is not.

Maybe `display-comint-buffer-action' should default to
`display-buffer-in-previous-window'?

-- 
Sam Steingold (https://aphar.dreamwidth.org/) on Pop 22.04 (jammy) X 11.0.12101004
https://lastingimpactpsychology.com https://steingoldpsychology.com
https://ij.org/ https://camera.org https://honestreporting.com
Legends are time-tested rumors.






  reply	other threads:[~2023-06-09 20:00 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
2023-06-09 20:00       ` Sam Steingold [this message]
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

  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=87o7lojthj.fsf@gnu.org \
    --to=sds@gnu.org \
    --cc=63956@debbugs.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 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).