AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Set up texmaker and miktex windows3/7/2024 ![]() TeX Live does not have that in the immediate install because they support so many platforms that keeping up with all the versions of Perl, where the various directories are located, etc., is just not possible. First, people are talking about on-the-fly. But - since what else can a person do with opinions except spread them around? - I speak to choosing TL in a blog post that you may find interesting. To answer the question in the title: On Windows, MiKTeX is much more popular.Īs to which one to get, you are not going to go wrong with either and the differences are very small. It is an interesting discussion, for sure. ![]() It's just a matter of scanning the hidden folder for the synctex file and then making sure any references in it point to the correct PDF location. It's also not that difficult to implement. If the option existed, PDF viewers would add support sooner or later. Using this as justification against implementing an option to hide synctex files is not a good argument i.m.o (seems a bit circular). The reason PDF viewers don't support different synctex locations is that there is no demand, because there's no convenient way to put the synctex files somewhere else. ![]() What you do or can do with the files after compiling really should not dictate the functionality of build tools like latexmk. Which is why I wish build tools or compilers would support this. My TeX editor supports hidden synctex files, but it's not available on other OSes, which makes working on multiple OSes/devices difficult. pdf files in your WD (and a hidden folder), there's not really a way to easily achieve this without involving scripts and moving files around after every compilation. I'm trying to make a point for better control over where files end up after compiling. I just like them tugged away where they don't get in the way :) Using a cleaning tool is obviously a good way to get a clean Workspace, but I personally like to have the LaTex files around just in case I need them for debugging. ![]() Including the PDF of course, which I personally want to keep next to the coreponding. If somebody really wants all files produced by LaTex to be moved into a sepereate folder, the output directory option does that. So eather you want synctex to work, or you disable it. You can not agree with this definition as much as you want, but not handeling synctex files this way would break most pdf viewers synctex implementations. MikTex implements this directly for the pdflatex command (and friends) and i assume u/m_spitfire wanted to make me aware that this behaviour also exists via latexmk on TexLive. This is also not my opinion, but rather the way it is implemented and why it is implemented that way.
0 Comments
Read More
Leave a Reply. |