Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
it-tricks [2024/03/05 18:04] popel [LaTeX, pdf] |
it-tricks [2024/05/23 09:58] (current) stepanek [Editors] |
||
---|---|---|---|
Line 8: | Line 8: | ||
* **vim**: Ondřej Bojar, Ruda Rosa, Milan Straka (C++ completion, Python completion, asynchronous make), ... | * **vim**: Ondřej Bojar, Ruda Rosa, Milan Straka (C++ completion, Python completion, asynchronous make), ... | ||
* to start learning vim, run the '' | * to start learning vim, run the '' | ||
- | * **emacs**: | + | * **emacs**: |
* **nano**: | * **nano**: | ||
* **IntelliJ IDEA**: Jonáš Vidra | * **IntelliJ IDEA**: Jonáš Vidra | ||
Line 97: | Line 97: | ||
* If you need a pdf-a validator (e.g. for your thesis), you can use `/ | * If you need a pdf-a validator (e.g. for your thesis), you can use `/ | ||
+ | ==== Faster LaTeX compilation ==== | ||
+ | * You should delete the packages you don't need from the preambule (not only for speed reasons). | ||
+ | * Include just the chapter (or section) you are currently working on, i.e. comment out the inclusion of other chapters or use '' | ||
+ | * When separating e.g. each chapter into a separate file and each chapter starts on a new page, you can use '' | ||
+ | * You can use '' | ||
+ | * If you are using complex tikz pictures you can convert them first to pdf manually and include the pdfs, so they are not compiled again and again (or you can try the externalization library to do this automatically). | ||
+ | * And when compiling locally, you can use latexmk -pvc to automatically compile a given file whenever it is saved. This does not really speedup the compilation, | ||
===== TAR archive mounting ===== | ===== TAR archive mounting ===== | ||
If you work with data consisting of many small files, you **should** store them in tar archives to save inodes and use LUSTRE filesystem efficiently. There is a way to mount a tar archive to a specific directory in a similar way you would mount an ISO image. You can use this command to //mount// (read-only) ARCHIVE (possibly compressed) to DIRECTORY: | If you work with data consisting of many small files, you **should** store them in tar archives to save inodes and use LUSTRE filesystem efficiently. There is a way to mount a tar archive to a specific directory in a similar way you would mount an ISO image. You can use this command to //mount// (read-only) ARCHIVE (possibly compressed) to DIRECTORY: |