![]() ![]() You can't just put them on a flash drive and use them on someone else's computer, unless you also copy over the preamble package. It makes more sense to have exactly the packages you need loaded explicitly in the preamble of each document you write.Ĭreating a default preamble also makes your documents much less portable. ![]() This may not seem like a big deal, but in my experience it can get annoying quite quickly, because over time you will forget what's in your standard preamble. This means that you will have to remember which packages you always load if you ever need to look for documentation for example or to debug an error that might arise from one of the packages. For smaller packages this isn't much of an issue, but for large package like TikZ for example, this will increase the compilation time for those documents.Ĭreating a default preamble effectively hides the packages that any document is using from you. So you will effectively be loading packages you don't need. Practical reasonsĮven if you use some packages very frequently, it's likely that you will not need every package you load in your default preamble in every document. I also have created a class for writing conference abstracts, since they require very condensed formatting due to word/page size limits. For example, I have a package which I load when I write letters which contains macros for my signature etc. Now if you do have needs for a particular functionality then of course creating your own package makes sense. This doesn't meet either of these criteria, and so should probably not be implemented as a package or a class. Now what you are suggesting seems to be neither of these, but rather is just the list of \usepackage commands (perhaps with some added macros) that you commonly use in most of your documents. Customizing LaTeX - create a document class or a package?. ![]() See the following question for some discussion of the distinction. Conceptual argumentsĬonceptually, packages should add a specific set of functionality to a document of any kind.ĭocument classes, on the other hand, should provide the markup for a particular kind of document. But if you just find that in most of your documents you load the same sets of packages, I would not recommend this, but instead use your editor to save some sort of standard template documents. Of course, if you find yourself producing particular kinds of documents with a similar structure, there may be grounds to create a custom class or package for that kind of document. There are both conceptual and practical reasons for not doing so. Since this is longer than a comment, I will add it as an answer even though it's an answer that recommends not doing what you are asking. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |