-
-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supporting PDF builds #51
Comments
I don't know if it is feasible to include this directly into sphinx-autobuild. However, I'm using sphinx-autobuild for updating the LaTeX output and at the same time latexmk in "preview continuous" mode. I have to start two processes (in two terminals), but apart from that, the update of the PDF happens automatically. I don't know about your additional build steps, but Additional information: |
Thanks for the info, latexmk sounds like a very good idea. Well then, my question would be - would it be possible to have a flag not to turn on the built-in web server? If you just want to build LaTeX, that's kind of unnecessary. |
This comment has been minimized.
This comment has been minimized.
AFAIK, this should be possible today with |
Hi @pradyunsg thanks for the question. I meant latexpdf, which is not available as an option? Since then I moved away from using sphinx-autobuild; generally speaking I wanted to get a single command in one terminal (some of my users are not advanced in Sphinx/bash) and no server to be launched (not needed for a PDF). Seems like this is not something that's planned to be implemented, which is OK :) |
It'll be
I personally don't see why having a redundant server that doesn't affect anything about the builds is an issue TBH. Worst case, it's eating an I/O port since the server basically sits idle unless there's a network request. Given that you're on a different workflow now, I think it's perfectly fine to defer this until someone else asks for behavior like this. :) |
That's what I meant. Perhaps I just have a wrong version or something. |
Actually it's 'cause
|
It seems this is not a valid solution as $ sphinx-autobuild -M latexpdf "." "_build"
usage: sphinx-autobuild [-h] [--port PORT] [--host HOST] [--re-ignore RE_IGNORE] [--ignore IGNORE] [--no-initial] [--open-browser]
[--delay DELAY] [--watch DIR] [--pre-build COMMAND] [--version]
sourcedir outdir [filenames ...]
sphinx-autobuild: error: unrecognized arguments: -M |
@AA-Turner is this also solved now by your recent patch? (I didn't check). |
I was wondering if it would be possible to use sphinx-autobuild also for PDF output. Since viewers like evince support reloading documents on change, it is actually just as convenient as previewing in the browser, and much of the documentation we generate is intended for PDF usage.
Currently I am using a dirty script which reruns
make latexpdf
every time files change, but it would be interesting to move to sphinx-autobuild if possible.The problem with using
sphinx-autobuild
easily is that it replacessphinx-build
, while in realitymake latexpdf
is two actions (for me actually three actions, as I also usetexfot
to filter tex output, but that's just an extension of the same problem) -sphinx-build
andmake all-pdf
.Would anyone have any ideas how to do that using sphinx-autobuild? This could be a useful feature in general.
The text was updated successfully, but these errors were encountered: