Latex structure preamble [closed]
What is the best way to separately store a config file with all the packages, commands etc. that come before the begin{document}
. I think this is called a preamble.
Currently I have a main.tex file with lots of separate include{sections}
within my main body. However I would also like to have a separate Tex file with the preamble contents to make my main.tex file look a bit more concise.
packages preamble
closed as off-topic by Christian Hupfer, Zarko, Fran, TeXnician, Circumscribe Jan 13 at 15:06
- This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.
|
show 1 more comment
What is the best way to separately store a config file with all the packages, commands etc. that come before the begin{document}
. I think this is called a preamble.
Currently I have a main.tex file with lots of separate include{sections}
within my main body. However I would also like to have a separate Tex file with the preamble contents to make my main.tex file look a bit more concise.
packages preamble
closed as off-topic by Christian Hupfer, Zarko, Fran, TeXnician, Circumscribe Jan 13 at 15:06
- This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.
1
You can save all the code from the preamble in a separate .tex file and call it withinclude
.
– Felix Phl
Jan 13 at 13:03
6
If you need a common set of packages and user defined macros all over again for most of your documents, it's really better to make a separate input file for that, either as own package or inclusion withinput
.
– Christian Hupfer
Jan 13 at 13:03
Thanks I have tried this and it works
– Mellow
Jan 13 at 13:13
1
@FelixPhl It's better toinput
a preamble thaninclude
it. That way you can stillinclude
the sections, and also use theincludeonly
mechanism.
– Teepeemm
Jan 13 at 13:37
3
I'm voting to close this question as off-topic because it was solved by comments.
– Zarko
Jan 13 at 14:34
|
show 1 more comment
What is the best way to separately store a config file with all the packages, commands etc. that come before the begin{document}
. I think this is called a preamble.
Currently I have a main.tex file with lots of separate include{sections}
within my main body. However I would also like to have a separate Tex file with the preamble contents to make my main.tex file look a bit more concise.
packages preamble
What is the best way to separately store a config file with all the packages, commands etc. that come before the begin{document}
. I think this is called a preamble.
Currently I have a main.tex file with lots of separate include{sections}
within my main body. However I would also like to have a separate Tex file with the preamble contents to make my main.tex file look a bit more concise.
packages preamble
packages preamble
edited Jan 13 at 13:07
Christian Hupfer
149k14195390
149k14195390
asked Jan 13 at 12:58
MellowMellow
214
214
closed as off-topic by Christian Hupfer, Zarko, Fran, TeXnician, Circumscribe Jan 13 at 15:06
- This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.
closed as off-topic by Christian Hupfer, Zarko, Fran, TeXnician, Circumscribe Jan 13 at 15:06
- This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.
1
You can save all the code from the preamble in a separate .tex file and call it withinclude
.
– Felix Phl
Jan 13 at 13:03
6
If you need a common set of packages and user defined macros all over again for most of your documents, it's really better to make a separate input file for that, either as own package or inclusion withinput
.
– Christian Hupfer
Jan 13 at 13:03
Thanks I have tried this and it works
– Mellow
Jan 13 at 13:13
1
@FelixPhl It's better toinput
a preamble thaninclude
it. That way you can stillinclude
the sections, and also use theincludeonly
mechanism.
– Teepeemm
Jan 13 at 13:37
3
I'm voting to close this question as off-topic because it was solved by comments.
– Zarko
Jan 13 at 14:34
|
show 1 more comment
1
You can save all the code from the preamble in a separate .tex file and call it withinclude
.
– Felix Phl
Jan 13 at 13:03
6
If you need a common set of packages and user defined macros all over again for most of your documents, it's really better to make a separate input file for that, either as own package or inclusion withinput
.
– Christian Hupfer
Jan 13 at 13:03
Thanks I have tried this and it works
– Mellow
Jan 13 at 13:13
1
@FelixPhl It's better toinput
a preamble thaninclude
it. That way you can stillinclude
the sections, and also use theincludeonly
mechanism.
– Teepeemm
Jan 13 at 13:37
3
I'm voting to close this question as off-topic because it was solved by comments.
– Zarko
Jan 13 at 14:34
1
1
You can save all the code from the preamble in a separate .tex file and call it with
include
.– Felix Phl
Jan 13 at 13:03
You can save all the code from the preamble in a separate .tex file and call it with
include
.– Felix Phl
Jan 13 at 13:03
6
6
If you need a common set of packages and user defined macros all over again for most of your documents, it's really better to make a separate input file for that, either as own package or inclusion with
input
.– Christian Hupfer
Jan 13 at 13:03
If you need a common set of packages and user defined macros all over again for most of your documents, it's really better to make a separate input file for that, either as own package or inclusion with
input
.– Christian Hupfer
Jan 13 at 13:03
Thanks I have tried this and it works
– Mellow
Jan 13 at 13:13
Thanks I have tried this and it works
– Mellow
Jan 13 at 13:13
1
1
@FelixPhl It's better to
input
a preamble than include
it. That way you can still include
the sections, and also use the includeonly
mechanism.– Teepeemm
Jan 13 at 13:37
@FelixPhl It's better to
input
a preamble than include
it. That way you can still include
the sections, and also use the includeonly
mechanism.– Teepeemm
Jan 13 at 13:37
3
3
I'm voting to close this question as off-topic because it was solved by comments.
– Zarko
Jan 13 at 14:34
I'm voting to close this question as off-topic because it was solved by comments.
– Zarko
Jan 13 at 14:34
|
show 1 more comment
0
active
oldest
votes
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
You can save all the code from the preamble in a separate .tex file and call it with
include
.– Felix Phl
Jan 13 at 13:03
6
If you need a common set of packages and user defined macros all over again for most of your documents, it's really better to make a separate input file for that, either as own package or inclusion with
input
.– Christian Hupfer
Jan 13 at 13:03
Thanks I have tried this and it works
– Mellow
Jan 13 at 13:13
1
@FelixPhl It's better to
input
a preamble thaninclude
it. That way you can stillinclude
the sections, and also use theincludeonly
mechanism.– Teepeemm
Jan 13 at 13:37
3
I'm voting to close this question as off-topic because it was solved by comments.
– Zarko
Jan 13 at 14:34