all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Simen Heggestøyl" <simenheg@gmail.com>
Cc: stefan@merten-home.de, 30063@debbugs.gnu.org
Subject: bug#30063: 26.0.90; Silent fail with `rst-compile-pdf-preview'
Date: Sun, 29 Sep 2019 14:09:06 +0200	[thread overview]
Message-ID: <87o8z3mhi5.fsf@gnus.org> (raw)
In-Reply-To: <1517054395.9954.0@smtp.gmail.com> ("Simen \=\?utf-8\?Q\?Heggest\?\= \=\?utf-8\?Q\?\=C3\=B8yl\=22's\?\= message of "Sat, 27 Jan 2018 12:59:55 +0100")

Simen Heggestøyl <simenheg@gmail.com> writes:

> * lisp/textmodes/rst.el (rst-compile-pdf-preview): Warn about missing
> executables when attempting to compile and preview an RST file as PDF.
> (Bug#30218)

[...]

> +    (unless (executable-find pdf-compile-program)
> +      (error "Cannot find executable `%s'" pdf-compile-program))
> +    (unless (executable-find rst-pdf-program)
> +      (error "Cannot find executable `%s'" rst-pdf-program))

Others pointed out that it might be nice to report error messages back
from the pdf commands, and that's true, but I think this patch makes
sense, too, because it gives good, early feedback on a likely problem,
so I think it should be applied.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2019-09-29 12:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 13:57 bug#30063: 26.0.90; Silent fail with `rst-compile-pdf-preview' Simen Heggestøyl
2018-01-27 11:59 ` Simen Heggestøyl
2018-01-28 18:11   ` Noam Postavsky
2018-01-29 17:43     ` Glenn Morris
2018-01-30 13:49     ` Eli Zaretskii
2018-01-30 14:30       ` Noam Postavsky
2018-01-30 15:40         ` Eli Zaretskii
2019-09-29 12:09   ` Lars Ingebrigtsen [this message]
2019-10-03 20:53     ` Stefan Merten
2019-10-07  3:25       ` Lars Ingebrigtsen
2019-10-09 16:13         ` Simen Heggestøyl

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=87o8z3mhi5.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=30063@debbugs.gnu.org \
    --cc=simenheg@gmail.com \
    --cc=stefan@merten-home.de \
    /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.