From: Jeff Norden <norden.jeff@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63956@debbugs.gnu.org, sds@gnu.org, monnier@iro.umontreal.ca
Subject: bug#63956: 29.0.91; tex-mode display problem in emacs-29
Date: Sun, 11 Jun 2023 15:12:08 -0500 [thread overview]
Message-ID: <CAPbFCnkCga6U7acgR3gmmC7OFZySVDtmXwSHc8d+Qy2qBW=Ycg@mail.gmail.com> (raw)
In-Reply-To: <83pm61yigx.fsf@gnu.org>
On Sun, Jun 11, 2023 at 1:14 PM Eli Zaretskii wrote:
> ...
> > 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?
Took me a bit to figure that out. Choosing the docview option from
`tex-compile' results in pre-pending "tex-cmd-" to "doc-view" and then
calling `tex-cmd-doc-view', which simply opens the pdf file (in
docview mode) with pop-to-buffer. The other tex-compile commands that
preview the document do so by running an external program such as
ghostview or xdvi. That is why I was thinking that opening in a new
frame might be appropriate.
I've never used tex-compile, and I wonder if it gets much use in
general. One of the ideas I was thinking of was adding it as a
sub-menu of the TeX menubar entry, which would make it easier to use.
Another thing, which I now realize is already listed as a 'fixme' item
in tex-mode.el, is to check that, e.g., the corresponding pdf file is
up to date (newer than the tex source) before previewing it.
-Jeff
next prev parent reply other threads:[~2023-06-11 20:12 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
2023-06-11 20:12 ` Jeff Norden [this message]
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='CAPbFCnkCga6U7acgR3gmmC7OFZySVDtmXwSHc8d+Qy2qBW=Ycg@mail.gmail.com' \
--to=norden.jeff@gmail.com \
--cc=63956@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--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.