emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Avoid ignoring LaTeX export output errors when org-latex-pdf-process is a list
Date: Thu, 26 May 2022 12:49:55 +0800	[thread overview]
Message-ID: <87leuo6gp8.fsf@localhost> (raw)
In-Reply-To: <t6iss2$60r$1@ciao.gmane.io>

Max Nikulin <manikulin@gmail.com> writes:

> On 22/05/2022 10:51, Ihor Radchenko wrote:
>> The attached patch is fixing a rather annoying problem when
>> org-latex-pdf-process is set to a list. Currently, only output of the
>> last command in the list is preserved in *Org PDF LaTeX output* buffer,
>> which sometimes prevents ox-latex from detecting compilation warnings.
> I may be wrong, but I believed that some code might check buffer content 
> for specific messages to determine if additional pass is required to 
> resolve or adjust cross-reference links. If it is done by external tools 
> working with log files than there is no problem, otherwise lisp code 
> analyzing whole buffer may be confusing by first pass messages when 
> there was no e.g. .aux file.

There is no such code. Otherwise, org-latex-pdf-process would be a lot
more constrained.


  reply	other threads:[~2022-05-26  4:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22  3:51 [PATCH] Avoid ignoring LaTeX export output errors when org-latex-pdf-process is a list Ihor Radchenko
2022-05-22 17:03 ` Daniel Fleischer
2022-05-26  4:44   ` Ihor Radchenko
2022-05-23  8:53 ` Eric S Fraga
2022-05-24 15:16 ` Max Nikulin
2022-05-26  4:49   ` Ihor Radchenko [this message]
2022-07-31  7:36 ` Ihor Radchenko

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87leuo6gp8.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \


* 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


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