unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sebastian Miele <iota@whxvd.name>
To: Juri Linkov <juri@linkov.net>
Cc: 74457@debbugs.gnu.org
Subject: bug#74457: 30.0.92; `display-tex-shell-buffer' contains `(inhibit-same-window . t)'
Date: Fri, 22 Nov 2024 06:03:10 +0100	[thread overview]
Message-ID: <932e83a2-96fe-444c-b6d1-d041493ece94@whxvd.name> (raw)
In-Reply-To: <87a5dsfogp.fsf@mail.linkov.net>

Am 2024-11-21 um 19:09 schrieb Juri Linkov:
>> `display-tex-shell-buffer' (defined in `window') is marked obsolete with
>> the message "use a `(category . tex-shell)' condition in
>> `display-buffer-alist'."
>>
>> The default value of `display-tex-shell-buffer' contains
>> `(inhibit-same-window . t)'.  I feel that doing
>>
>>    (add-to-list 'display-buffer-alist
>>                 (cons t (cons #'display-buffer-same-window nil)))
>>
>> should have the desired effect of displaying a TeX shell buffer in the
>> same window (when compiling TeX files in latex-mode), without having to
>> alter the value of the obsolete variable `display-tex-shell-buffer'.
>> But `(inhibit-same-window . t)' in the default value prevents that from
>> happening.  Instead another frame is popped up or reused.
> 
> You can override `inhibit-same-window' by the corresponding category:
> 
>    (add-to-list 'display-buffer-alist
>                 '((category . tex-shell)
>                   (display-buffer-same-window)
>                   (inhibit-same-window . nil)))

Thank you.  That works.





  reply	other threads:[~2024-11-22  5:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 11:01 bug#74457: 30.0.92; `display-tex-shell-buffer' contains `(inhibit-same-window . t)' Sebastian Miele
2024-11-21 18:09 ` Juri Linkov
2024-11-22  5:03   ` Sebastian Miele [this message]
2024-11-22  7:33     ` Juri Linkov
2024-11-22  8:23       ` Eli Zaretskii
2024-11-23 18:30         ` Juri Linkov

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=932e83a2-96fe-444c-b6d1-d041493ece94@whxvd.name \
    --to=iota@whxvd.name \
    --cc=74457@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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).