How to detect whether PassOptionsToPackage was already called?
If I call:
PassOptionsToPackage{backend=biber,style=numeric,backref=false}{biblatex}
% And later someone else call again
PassOptionsToPackage{style=abnt,backend=biber}{biblatex}
What will happen?
Can I detect whether someone else had already called PassOptionsToPackage and do not override their definitions?
optional-arguments package-options class-options options
add a comment |
If I call:
PassOptionsToPackage{backend=biber,style=numeric,backref=false}{biblatex}
% And later someone else call again
PassOptionsToPackage{style=abnt,backend=biber}{biblatex}
What will happen?
Can I detect whether someone else had already called PassOptionsToPackage and do not override their definitions?
optional-arguments package-options class-options options
add a comment |
If I call:
PassOptionsToPackage{backend=biber,style=numeric,backref=false}{biblatex}
% And later someone else call again
PassOptionsToPackage{style=abnt,backend=biber}{biblatex}
What will happen?
Can I detect whether someone else had already called PassOptionsToPackage and do not override their definitions?
optional-arguments package-options class-options options
If I call:
PassOptionsToPackage{backend=biber,style=numeric,backref=false}{biblatex}
% And later someone else call again
PassOptionsToPackage{style=abnt,backend=biber}{biblatex}
What will happen?
Can I detect whether someone else had already called PassOptionsToPackage and do not override their definitions?
optional-arguments package-options class-options options
optional-arguments package-options class-options options
asked 5 hours ago
useruser
1,2602930
1,2602930
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The definition of PassOptionsToPackage is
% latex.ltx, line 7784:
defPassOptionsToPackage{@pass@ptions@pkgextension}
and we can look at @pass@ptions:
% latex.ltx, line 7778:
def@pass@ptions#1#2#3{%
expandafterxdefcsname opt@#3.#1endcsname{%
@ifundefined{opt@#3.#1}@empty
{csname opt@#3.#1endcsname,}%
zap@space#2 @empty}}
Suppose we call PassOptionsToPackage{baz}{foo}. If opt@foo.sty (can only be formed with csname) is undefined, it is defined to expand to baz. If it is already defined, say to gnu,gnat, then it will be redefined to expand to gnu,gnat,baz.
The latter case can happen either if PassOptionsToPackage{...}{foo} has already been called or the package has already been loaded. In the second case PassOptionsToPackage{baz}{foo} does nothing.
As you see, new sets of options are chained to the already existing ones. It's then a job of the package, when loaded, to make its way amongst them.
This should also answer your question about detection: you can use
ifcsname opt@foo.styendcsname
<options have already been passed or the package has already been loaded>
else
<no options have been passed yet>
fi
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%2f483570%2fhow-to-detect-whether-passoptionstopackage-was-already-called%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
The definition of PassOptionsToPackage is
% latex.ltx, line 7784:
defPassOptionsToPackage{@pass@ptions@pkgextension}
and we can look at @pass@ptions:
% latex.ltx, line 7778:
def@pass@ptions#1#2#3{%
expandafterxdefcsname opt@#3.#1endcsname{%
@ifundefined{opt@#3.#1}@empty
{csname opt@#3.#1endcsname,}%
zap@space#2 @empty}}
Suppose we call PassOptionsToPackage{baz}{foo}. If opt@foo.sty (can only be formed with csname) is undefined, it is defined to expand to baz. If it is already defined, say to gnu,gnat, then it will be redefined to expand to gnu,gnat,baz.
The latter case can happen either if PassOptionsToPackage{...}{foo} has already been called or the package has already been loaded. In the second case PassOptionsToPackage{baz}{foo} does nothing.
As you see, new sets of options are chained to the already existing ones. It's then a job of the package, when loaded, to make its way amongst them.
This should also answer your question about detection: you can use
ifcsname opt@foo.styendcsname
<options have already been passed or the package has already been loaded>
else
<no options have been passed yet>
fi
add a comment |
The definition of PassOptionsToPackage is
% latex.ltx, line 7784:
defPassOptionsToPackage{@pass@ptions@pkgextension}
and we can look at @pass@ptions:
% latex.ltx, line 7778:
def@pass@ptions#1#2#3{%
expandafterxdefcsname opt@#3.#1endcsname{%
@ifundefined{opt@#3.#1}@empty
{csname opt@#3.#1endcsname,}%
zap@space#2 @empty}}
Suppose we call PassOptionsToPackage{baz}{foo}. If opt@foo.sty (can only be formed with csname) is undefined, it is defined to expand to baz. If it is already defined, say to gnu,gnat, then it will be redefined to expand to gnu,gnat,baz.
The latter case can happen either if PassOptionsToPackage{...}{foo} has already been called or the package has already been loaded. In the second case PassOptionsToPackage{baz}{foo} does nothing.
As you see, new sets of options are chained to the already existing ones. It's then a job of the package, when loaded, to make its way amongst them.
This should also answer your question about detection: you can use
ifcsname opt@foo.styendcsname
<options have already been passed or the package has already been loaded>
else
<no options have been passed yet>
fi
add a comment |
The definition of PassOptionsToPackage is
% latex.ltx, line 7784:
defPassOptionsToPackage{@pass@ptions@pkgextension}
and we can look at @pass@ptions:
% latex.ltx, line 7778:
def@pass@ptions#1#2#3{%
expandafterxdefcsname opt@#3.#1endcsname{%
@ifundefined{opt@#3.#1}@empty
{csname opt@#3.#1endcsname,}%
zap@space#2 @empty}}
Suppose we call PassOptionsToPackage{baz}{foo}. If opt@foo.sty (can only be formed with csname) is undefined, it is defined to expand to baz. If it is already defined, say to gnu,gnat, then it will be redefined to expand to gnu,gnat,baz.
The latter case can happen either if PassOptionsToPackage{...}{foo} has already been called or the package has already been loaded. In the second case PassOptionsToPackage{baz}{foo} does nothing.
As you see, new sets of options are chained to the already existing ones. It's then a job of the package, when loaded, to make its way amongst them.
This should also answer your question about detection: you can use
ifcsname opt@foo.styendcsname
<options have already been passed or the package has already been loaded>
else
<no options have been passed yet>
fi
The definition of PassOptionsToPackage is
% latex.ltx, line 7784:
defPassOptionsToPackage{@pass@ptions@pkgextension}
and we can look at @pass@ptions:
% latex.ltx, line 7778:
def@pass@ptions#1#2#3{%
expandafterxdefcsname opt@#3.#1endcsname{%
@ifundefined{opt@#3.#1}@empty
{csname opt@#3.#1endcsname,}%
zap@space#2 @empty}}
Suppose we call PassOptionsToPackage{baz}{foo}. If opt@foo.sty (can only be formed with csname) is undefined, it is defined to expand to baz. If it is already defined, say to gnu,gnat, then it will be redefined to expand to gnu,gnat,baz.
The latter case can happen either if PassOptionsToPackage{...}{foo} has already been called or the package has already been loaded. In the second case PassOptionsToPackage{baz}{foo} does nothing.
As you see, new sets of options are chained to the already existing ones. It's then a job of the package, when loaded, to make its way amongst them.
This should also answer your question about detection: you can use
ifcsname opt@foo.styendcsname
<options have already been passed or the package has already been loaded>
else
<no options have been passed yet>
fi
answered 4 hours ago
egregegreg
732k8919303253
732k8919303253
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%2f483570%2fhow-to-detect-whether-passoptionstopackage-was-already-called%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