-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Previewer is hard-coded to use PdfLaTeX #302
Comments
Yes I also noticed this when using LuaLaTeX with fontspec and is something which should definitely be dynamic. Possibly the cleanest solution would be to just use the program for the current document (so we obey the default program from the settings and also make it overwriteable using the magic comments). Is this were the preview logic is implemented? texstudio/src/buildmanager.cpp Line 1788 in fc2c012
|
looks like it |
I do not know whether this is linked or not, but the fact that the previewing tool is different from the compilation tool might cause some strange behaviour like this one: https://tex.stackexchange.com/questions/718530/pdftex-log-file-eating-up-disk-space Mayhap automatically changing the preview tool so that it's identical to the compilation tool would avoid this kind of problem? |
more options are available |
@sunderme what exactly do you mean by that? If you mean that the user can choose between different visualization tools, this has been the case for quite some time, cf. the point I mentioned above was more about having TeXStudio automatically switch to the pre-visualization tool corresponding to the compilation toolchain, i.e. choosing lualatex previz when compiling with lualatex, xelatex previz when compiling with xelatex, etc. I reckon that this latter point is not exactly what the OP asked for though. Do you think I should open a new issue / enhancement for these latter considerations? |
The issue is quite old. |
Very much indeed, and I am the one who created it, I forgot >.< Here it is, for reference, and sorry about the noise, #3851 |
I use XeLaTeX to compile my documents, so they contain some special code (like font selection). But internal previewer is hard-coded to use either PdfLaTeX or plain LaTeX. It works fine if I set the “PdfLaTeX” option to
xelatex
, though, but that makes me unable to use true PdfLaTeX for documents that require that.Environment
The text was updated successfully, but these errors were encountered: