Relocate style files for metropolis presentation
I have adjusted the style files for the metropolis beamer style by adjusting the beamercolorthememetropolis.sty
file and placed the new file inside the main folder of my project.
If I then run the following MWE everything goes fine:
documentclass{beamer}
usetheme{metropolis}
begin{document}
begin{frame}{test} test end{frame}
end{document}
My problem is that this clutters my file management and that I would rather have the new beamercolorthememetropolis.sty
file in a subfolder. My attempt was:
documentclass{beamer}
usetheme{metropolis}
usepackage{./Preliminaries/beamercolorthememetropolis}
begin{document}
begin{frame}[fragile]{titel} test end{frame}
end{document}
But this spits out various errors e.g.:
LaTeX Warning: You have requested package `./Preliminaries/beamercolorthememetr opolis',
but the package provides `beamercolorthememetropolis'.
Package: beamercolorthememetropolis 2015/12/04 Metropolis color theme ) (./Preliminaries/beamerinnerthememetropolis.sty
! LaTeX Error: Command metropolis@inner@setdefaults already defined.
Or name end... illegal, see p.192 of the manual.
See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ...
l.49 }
Your command was ignored. Type I <command> <return> to replace it with another command, or <return> to continue without it.
It would appear that my usepackage fails to overwrite some settings that are present in the stock version of metropolis if I include them in this fashion...
beamer packages beamer-metropolis
|
show 2 more comments
I have adjusted the style files for the metropolis beamer style by adjusting the beamercolorthememetropolis.sty
file and placed the new file inside the main folder of my project.
If I then run the following MWE everything goes fine:
documentclass{beamer}
usetheme{metropolis}
begin{document}
begin{frame}{test} test end{frame}
end{document}
My problem is that this clutters my file management and that I would rather have the new beamercolorthememetropolis.sty
file in a subfolder. My attempt was:
documentclass{beamer}
usetheme{metropolis}
usepackage{./Preliminaries/beamercolorthememetropolis}
begin{document}
begin{frame}[fragile]{titel} test end{frame}
end{document}
But this spits out various errors e.g.:
LaTeX Warning: You have requested package `./Preliminaries/beamercolorthememetr opolis',
but the package provides `beamercolorthememetropolis'.
Package: beamercolorthememetropolis 2015/12/04 Metropolis color theme ) (./Preliminaries/beamerinnerthememetropolis.sty
! LaTeX Error: Command metropolis@inner@setdefaults already defined.
Or name end... illegal, see p.192 of the manual.
See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ...
l.49 }
Your command was ignored. Type I <command> <return> to replace it with another command, or <return> to continue without it.
It would appear that my usepackage fails to overwrite some settings that are present in the stock version of metropolis if I include them in this fashion...
beamer packages beamer-metropolis
1
If you change something inside a sty file, you need to give it a new name, otherwise you violet tex licence. If the changes are not too substantial I would leave the sty files alone and do the changes within you tex file.
– samcarter
Jun 24 '17 at 13:33
Ok, I did not know this. (does this count when I do not plan on redistributing them. It's useful to retain the original name so that I retain the original package's structure) Also, would this fix my problem or is this merely a "style" change ?
– gertian
Jun 24 '17 at 13:39
Yes, even if you do not redistribute the code, the original code is still under LPPL. see latex-project.org/lppl for more information
– samcarter
Jun 24 '17 at 13:43
What did you change in the colour theme? I suspect this can be probably be done from the main file or maybe the changes themself can be placed in a new new color theme.
– samcarter
Jun 24 '17 at 13:46
If you copy the complete metropolis theme, give it a new name and make your changes in the colour theme and change the names in the theme .sty file, you just have to loadusetheme{TheFifthElement}
and no extra call for your modified colour theme, so you won't run into the problem you describe above.
– samcarter
Jun 24 '17 at 13:49
|
show 2 more comments
I have adjusted the style files for the metropolis beamer style by adjusting the beamercolorthememetropolis.sty
file and placed the new file inside the main folder of my project.
If I then run the following MWE everything goes fine:
documentclass{beamer}
usetheme{metropolis}
begin{document}
begin{frame}{test} test end{frame}
end{document}
My problem is that this clutters my file management and that I would rather have the new beamercolorthememetropolis.sty
file in a subfolder. My attempt was:
documentclass{beamer}
usetheme{metropolis}
usepackage{./Preliminaries/beamercolorthememetropolis}
begin{document}
begin{frame}[fragile]{titel} test end{frame}
end{document}
But this spits out various errors e.g.:
LaTeX Warning: You have requested package `./Preliminaries/beamercolorthememetr opolis',
but the package provides `beamercolorthememetropolis'.
Package: beamercolorthememetropolis 2015/12/04 Metropolis color theme ) (./Preliminaries/beamerinnerthememetropolis.sty
! LaTeX Error: Command metropolis@inner@setdefaults already defined.
Or name end... illegal, see p.192 of the manual.
See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ...
l.49 }
Your command was ignored. Type I <command> <return> to replace it with another command, or <return> to continue without it.
It would appear that my usepackage fails to overwrite some settings that are present in the stock version of metropolis if I include them in this fashion...
beamer packages beamer-metropolis
I have adjusted the style files for the metropolis beamer style by adjusting the beamercolorthememetropolis.sty
file and placed the new file inside the main folder of my project.
If I then run the following MWE everything goes fine:
documentclass{beamer}
usetheme{metropolis}
begin{document}
begin{frame}{test} test end{frame}
end{document}
My problem is that this clutters my file management and that I would rather have the new beamercolorthememetropolis.sty
file in a subfolder. My attempt was:
documentclass{beamer}
usetheme{metropolis}
usepackage{./Preliminaries/beamercolorthememetropolis}
begin{document}
begin{frame}[fragile]{titel} test end{frame}
end{document}
But this spits out various errors e.g.:
LaTeX Warning: You have requested package `./Preliminaries/beamercolorthememetr opolis',
but the package provides `beamercolorthememetropolis'.
Package: beamercolorthememetropolis 2015/12/04 Metropolis color theme ) (./Preliminaries/beamerinnerthememetropolis.sty
! LaTeX Error: Command metropolis@inner@setdefaults already defined.
Or name end... illegal, see p.192 of the manual.
See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ...
l.49 }
Your command was ignored. Type I <command> <return> to replace it with another command, or <return> to continue without it.
It would appear that my usepackage fails to overwrite some settings that are present in the stock version of metropolis if I include them in this fashion...
beamer packages beamer-metropolis
beamer packages beamer-metropolis
edited Jan 15 at 19:43
samcarter
87.9k797281
87.9k797281
asked Jun 24 '17 at 12:15
gertiangertian
1827
1827
1
If you change something inside a sty file, you need to give it a new name, otherwise you violet tex licence. If the changes are not too substantial I would leave the sty files alone and do the changes within you tex file.
– samcarter
Jun 24 '17 at 13:33
Ok, I did not know this. (does this count when I do not plan on redistributing them. It's useful to retain the original name so that I retain the original package's structure) Also, would this fix my problem or is this merely a "style" change ?
– gertian
Jun 24 '17 at 13:39
Yes, even if you do not redistribute the code, the original code is still under LPPL. see latex-project.org/lppl for more information
– samcarter
Jun 24 '17 at 13:43
What did you change in the colour theme? I suspect this can be probably be done from the main file or maybe the changes themself can be placed in a new new color theme.
– samcarter
Jun 24 '17 at 13:46
If you copy the complete metropolis theme, give it a new name and make your changes in the colour theme and change the names in the theme .sty file, you just have to loadusetheme{TheFifthElement}
and no extra call for your modified colour theme, so you won't run into the problem you describe above.
– samcarter
Jun 24 '17 at 13:49
|
show 2 more comments
1
If you change something inside a sty file, you need to give it a new name, otherwise you violet tex licence. If the changes are not too substantial I would leave the sty files alone and do the changes within you tex file.
– samcarter
Jun 24 '17 at 13:33
Ok, I did not know this. (does this count when I do not plan on redistributing them. It's useful to retain the original name so that I retain the original package's structure) Also, would this fix my problem or is this merely a "style" change ?
– gertian
Jun 24 '17 at 13:39
Yes, even if you do not redistribute the code, the original code is still under LPPL. see latex-project.org/lppl for more information
– samcarter
Jun 24 '17 at 13:43
What did you change in the colour theme? I suspect this can be probably be done from the main file or maybe the changes themself can be placed in a new new color theme.
– samcarter
Jun 24 '17 at 13:46
If you copy the complete metropolis theme, give it a new name and make your changes in the colour theme and change the names in the theme .sty file, you just have to loadusetheme{TheFifthElement}
and no extra call for your modified colour theme, so you won't run into the problem you describe above.
– samcarter
Jun 24 '17 at 13:49
1
1
If you change something inside a sty file, you need to give it a new name, otherwise you violet tex licence. If the changes are not too substantial I would leave the sty files alone and do the changes within you tex file.
– samcarter
Jun 24 '17 at 13:33
If you change something inside a sty file, you need to give it a new name, otherwise you violet tex licence. If the changes are not too substantial I would leave the sty files alone and do the changes within you tex file.
– samcarter
Jun 24 '17 at 13:33
Ok, I did not know this. (does this count when I do not plan on redistributing them. It's useful to retain the original name so that I retain the original package's structure) Also, would this fix my problem or is this merely a "style" change ?
– gertian
Jun 24 '17 at 13:39
Ok, I did not know this. (does this count when I do not plan on redistributing them. It's useful to retain the original name so that I retain the original package's structure) Also, would this fix my problem or is this merely a "style" change ?
– gertian
Jun 24 '17 at 13:39
Yes, even if you do not redistribute the code, the original code is still under LPPL. see latex-project.org/lppl for more information
– samcarter
Jun 24 '17 at 13:43
Yes, even if you do not redistribute the code, the original code is still under LPPL. see latex-project.org/lppl for more information
– samcarter
Jun 24 '17 at 13:43
What did you change in the colour theme? I suspect this can be probably be done from the main file or maybe the changes themself can be placed in a new new color theme.
– samcarter
Jun 24 '17 at 13:46
What did you change in the colour theme? I suspect this can be probably be done from the main file or maybe the changes themself can be placed in a new new color theme.
– samcarter
Jun 24 '17 at 13:46
If you copy the complete metropolis theme, give it a new name and make your changes in the colour theme and change the names in the theme .sty file, you just have to load
usetheme{TheFifthElement}
and no extra call for your modified colour theme, so you won't run into the problem you describe above.– samcarter
Jun 24 '17 at 13:49
If you copy the complete metropolis theme, give it a new name and make your changes in the colour theme and change the names in the theme .sty file, you just have to load
usetheme{TheFifthElement}
and no extra call for your modified colour theme, so you won't run into the problem you describe above.– samcarter
Jun 24 '17 at 13:49
|
show 2 more comments
1 Answer
1
active
oldest
votes
You cannot modify a latex sty file and keep the same name as this violates LPPL licence.
I see a few alternatives
use the original metropolis theme and make the changes locally in in your beamer document. For example if you want to change some colour:
documentclass{beamer}
usetheme{metropolis}
setbeamercolor{frametitle}{fg=red, bg=blue}
begin{document}
begin{frame}
frametitle{test}
end{frame}
end{document}
if the changes are too numerous and clutter you document, you can outsource the changes into a new file, say
./preliminaries/changes.tex
andinput{./preliminaries/changes.tex}
it into your documentOr make a copy of the whole
beamertheme-metropolis
folder, rename all files therein which you want to change (remember to also change the package name and the names of the loaded sub-themes in what originally has been calledbeamerthememetropolis.sty
). If you prefer to have this new theme in a subfolder, you can adjust the paths to load the theme from a subfolder.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f376590%2frelocate-style-files-for-metropolis-presentation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You cannot modify a latex sty file and keep the same name as this violates LPPL licence.
I see a few alternatives
use the original metropolis theme and make the changes locally in in your beamer document. For example if you want to change some colour:
documentclass{beamer}
usetheme{metropolis}
setbeamercolor{frametitle}{fg=red, bg=blue}
begin{document}
begin{frame}
frametitle{test}
end{frame}
end{document}
if the changes are too numerous and clutter you document, you can outsource the changes into a new file, say
./preliminaries/changes.tex
andinput{./preliminaries/changes.tex}
it into your documentOr make a copy of the whole
beamertheme-metropolis
folder, rename all files therein which you want to change (remember to also change the package name and the names of the loaded sub-themes in what originally has been calledbeamerthememetropolis.sty
). If you prefer to have this new theme in a subfolder, you can adjust the paths to load the theme from a subfolder.
add a comment |
You cannot modify a latex sty file and keep the same name as this violates LPPL licence.
I see a few alternatives
use the original metropolis theme and make the changes locally in in your beamer document. For example if you want to change some colour:
documentclass{beamer}
usetheme{metropolis}
setbeamercolor{frametitle}{fg=red, bg=blue}
begin{document}
begin{frame}
frametitle{test}
end{frame}
end{document}
if the changes are too numerous and clutter you document, you can outsource the changes into a new file, say
./preliminaries/changes.tex
andinput{./preliminaries/changes.tex}
it into your documentOr make a copy of the whole
beamertheme-metropolis
folder, rename all files therein which you want to change (remember to also change the package name and the names of the loaded sub-themes in what originally has been calledbeamerthememetropolis.sty
). If you prefer to have this new theme in a subfolder, you can adjust the paths to load the theme from a subfolder.
add a comment |
You cannot modify a latex sty file and keep the same name as this violates LPPL licence.
I see a few alternatives
use the original metropolis theme and make the changes locally in in your beamer document. For example if you want to change some colour:
documentclass{beamer}
usetheme{metropolis}
setbeamercolor{frametitle}{fg=red, bg=blue}
begin{document}
begin{frame}
frametitle{test}
end{frame}
end{document}
if the changes are too numerous and clutter you document, you can outsource the changes into a new file, say
./preliminaries/changes.tex
andinput{./preliminaries/changes.tex}
it into your documentOr make a copy of the whole
beamertheme-metropolis
folder, rename all files therein which you want to change (remember to also change the package name and the names of the loaded sub-themes in what originally has been calledbeamerthememetropolis.sty
). If you prefer to have this new theme in a subfolder, you can adjust the paths to load the theme from a subfolder.
You cannot modify a latex sty file and keep the same name as this violates LPPL licence.
I see a few alternatives
use the original metropolis theme and make the changes locally in in your beamer document. For example if you want to change some colour:
documentclass{beamer}
usetheme{metropolis}
setbeamercolor{frametitle}{fg=red, bg=blue}
begin{document}
begin{frame}
frametitle{test}
end{frame}
end{document}
if the changes are too numerous and clutter you document, you can outsource the changes into a new file, say
./preliminaries/changes.tex
andinput{./preliminaries/changes.tex}
it into your documentOr make a copy of the whole
beamertheme-metropolis
folder, rename all files therein which you want to change (remember to also change the package name and the names of the loaded sub-themes in what originally has been calledbeamerthememetropolis.sty
). If you prefer to have this new theme in a subfolder, you can adjust the paths to load the theme from a subfolder.
answered Jun 24 '17 at 14:30
samcartersamcarter
87.9k797281
87.9k797281
add a comment |
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f376590%2frelocate-style-files-for-metropolis-presentation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
If you change something inside a sty file, you need to give it a new name, otherwise you violet tex licence. If the changes are not too substantial I would leave the sty files alone and do the changes within you tex file.
– samcarter
Jun 24 '17 at 13:33
Ok, I did not know this. (does this count when I do not plan on redistributing them. It's useful to retain the original name so that I retain the original package's structure) Also, would this fix my problem or is this merely a "style" change ?
– gertian
Jun 24 '17 at 13:39
Yes, even if you do not redistribute the code, the original code is still under LPPL. see latex-project.org/lppl for more information
– samcarter
Jun 24 '17 at 13:43
What did you change in the colour theme? I suspect this can be probably be done from the main file or maybe the changes themself can be placed in a new new color theme.
– samcarter
Jun 24 '17 at 13:46
If you copy the complete metropolis theme, give it a new name and make your changes in the colour theme and change the names in the theme .sty file, you just have to load
usetheme{TheFifthElement}
and no extra call for your modified colour theme, so you won't run into the problem you describe above.– samcarter
Jun 24 '17 at 13:49