unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jeff Norden <norden.jeff@gmail.com>, monnier@iro.umontreal.ca
Cc: 63956@debbugs.gnu.org, sds@gnu.org
Subject: bug#63956: 29.0.91; tex-mode display problem in emacs-29
Date: Sun, 11 Jun 2023 21:14:22 +0300	[thread overview]
Message-ID: <83pm61yigx.fsf@gnu.org> (raw)
In-Reply-To: <CAPbFCnnxcZbxM8qGK0kQ6SXB4OX_x7+UejUvEv4Jtz+fMUCOJw@mail.gmail.com> (message from Jeff Norden on Sun, 11 Jun 2023 12:31:54 -0500)

> From: Jeff Norden <norden.jeff@gmail.com>
> Date: Sun, 11 Jun 2023 12:31:54 -0500
> Cc: sds@gnu.org, 63956@debbugs.gnu.org, monnier@iro.umontreal.ca
> 
> On Sun, Jun 11, 2023 at 11:01 AM Eli Zaretskii <eliz@gnu.org> wrote:
> ...
> > > I suggest just removing the actions from the two display-buffer calls
> > > and the pop-top-buffer call in tex-mode.el.
> >
> > Meanwhile I installed a different fix: there's no a separate defcustom
> > display-tex-shell-buffer-action, whose default should do what you
> > want.  If it doesn't do what you want, please tell the details, and
> > let's take it from there.
> >
> > IOW, please try the latest emacs-29 branch of the Emacs Git
> > repository, and see if tex-mode there behaves better.
> 
> Works fine for me.

Great, thanks for testing.

> Using -tex-shell-buffer-action for a docview buffer is perhaps a bit
> odd

You could be right, but I couldn't find any callers of that function,
so it was hard for me to reason about that specific case.  Stefan,
since you introduced tex-cmd-doc-view into tex-mode.el, could you take
a look and tell whether using display-tex-shell-buffer-action in its
default value there makes sense?  If not, what would be a better
default?





  reply	other threads:[~2023-06-11 18:14 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
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 [this message]
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=83pm61yigx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63956@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=norden.jeff@gmail.com \
    --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 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).