tools/pdf: leave it to user to build epdfinfo
Trying to do this automatically is buggy to the point of insanity. It's not reliable enough to use as a :post-build target for the pdf-tools package. Better to fail gracefully, let the user know what they must do, and let them do it at their own discretion.
This commit is contained in:
parent
8424e0a780
commit
daa50557a4
2 changed files with 15 additions and 22 deletions
|
@ -3,19 +3,7 @@
|
|||
|
||||
(package! pdf-tools
|
||||
:recipe (:host github
|
||||
:repo "vedang/pdf-tools"
|
||||
:post-build
|
||||
(let ((warning-minimum-log-level :error))
|
||||
(require 'pdf-tools)
|
||||
(unless (file-exists-p pdf-info-epdfinfo-program)
|
||||
(require 'pdf-occur)
|
||||
(print-group!
|
||||
(print! (start "Building epdfinfo for pdf-tools"))
|
||||
(with-current-buffer (pdf-tools-install 'no-query)
|
||||
(while compilation-in-progress
|
||||
(sleep-for 1))
|
||||
(when (> compilation-num-errors-found 0)
|
||||
(print! (warn "Failed to build epdfinfo because: %s" (buffer-string)))))))))
|
||||
:repo "vedang/pdf-tools")
|
||||
:pin "d262cf9e19d57c6567e06e51d109150c20753839")
|
||||
|
||||
(package! saveplace-pdf-view :pin "54ed966b842501c3c092dbf57b372e37b033c578")
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue