How to detect whether PassOptionsToPackage was already called?How can one undefine an already processed class...

Why was the small council so happy for Tyrion to become the Master of Coin?

Have astronauts in space suits ever taken selfies? If so, how?

Modeling an IPv4 Address

How much RAM could one put in a typical 80386 setup?

Why did the Germans forbid the possession of pet pigeons in Rostov-on-Don in 1941?

The use of multiple foreign keys on same column in SQL Server

How is it possible to have an ability score that is less than 3?

Is it legal for company to use my work email to pretend I still work there?

How to write a macro that is braces sensitive?

How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?

Today is the Center

What do you call a Matrix-like slowdown and camera movement effect?

Why Is Death Allowed In the Matrix?

Languages that we cannot (dis)prove to be Context-Free

Is this a crack on the carbon frame?

What does "Puller Prush Person" mean?

Adding span tags within wp_list_pages list items

Expeditious Retreat

Writing rule stating superpower from different root cause is bad writing

What's the point of deactivating Num Lock on login screens?

TGV timetables / schedules?

How do I create uniquely male characters?

Why doesn't Newton's third law mean a person bounces back to where they started when they hit the ground?

Can a Warlock become Neutral Good?



How to detect whether PassOptionsToPackage was already called?


How can one undefine an already processed class option?Detect value of option given to documentclassHow to detect whether “I'm on arXiv.org”?Applying options to already loaded packageerror 'clipbox already defined' when use package adjustboxHow to DeclareOption with a variable?How to test whether report has been called with “draft” optionHow to detect whether a package supports an option, or not?How to declare several options for a packageDetect no argument in newcommand













1















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?










share|improve this question



























    1















    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?










    share|improve this question

























      1












      1








      1


      1






      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?










      share|improve this question














      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 7 hours ago









      useruser

      1,2602930




      1,2602930






















          1 Answer
          1






          active

          oldest

          votes


















          2














          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





          share|improve this answer
























            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
            });


            }
            });














            draft saved

            draft discarded


















            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









            2














            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





            share|improve this answer




























              2














              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





              share|improve this answer


























                2












                2








                2







                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





                share|improve this answer













                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






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 6 hours ago









                egregegreg

                732k8919303253




                732k8919303253






























                    draft saved

                    draft discarded




















































                    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.




                    draft saved


                    draft discarded














                    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





















































                    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







                    Popular posts from this blog

                    El tren de la libertad Índice Antecedentes "Porque yo decido" Desarrollo de la...

                    Castillo d'Acher Características Menú de navegación

                    Connecting two nodes from the same mother node horizontallyTikZ: What EXACTLY does the the |- notation for...