To be or not to be - Optional arguments inside defination of macro












1















The version A part in the following example is to define header/footer by macros from package fancyhdr.



Though this version is workable, it's a awkward achievement because the same part of code(ifnum...) is written twice.



Except the optional argument #2, all other code is exactly the same. To improve it, I tried the version B below, but it does not work at all.



It will be awfull especially when the same part of code is large.



So, to sumarize, is there a better way of handling optional arguments (to be there or not) to avoid heavy duplicate code.



documentclass{article}
usepackage{geometry,fancyhdr,xparse}
geometry{showframe}

begin{document}
pagestyle{fancy}
fancyhf{}

%Version A: workable %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
NewDocumentCommand{firstpage}{momm}{%
IfNoValueTF{#2}
{#1{%
ifnumvalue{page}=1
#3% content of header/footer only at the first page
else
#4% content of header/footer at the rest pages
fi
}
}
{#1[#2]% the only diferrence between the two branches of IfNoValueTF is, whether introducing the optional argument #2
{%
ifnumvalue{page}=1
#3% content of header/footer only at the first page
else
#4% content of header/footer at the rest pages
fi
}
}
}%firstpage

% Test
firstpage{fancyhead}[c]{only at the first page}{at rest pages}
firstpage{rhead}{r first}{r rest}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% Version B: not workable %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
NewDocumentCommand{firstpageA}{momm}{%
#1 IfNoValueTF{#2}{}{[#2]}
ifnumvalue{page}=1
#3% content of header/footer only at the first page
else
#4% content of header/footer at the rest pages
fi
}%firstpageA

% Test
firstpageA{fancyhead}[c]{only at the first page}{at rest pages}
firstpageA{rhead}{r first}{r rest}









share|improve this question





























    1















    The version A part in the following example is to define header/footer by macros from package fancyhdr.



    Though this version is workable, it's a awkward achievement because the same part of code(ifnum...) is written twice.



    Except the optional argument #2, all other code is exactly the same. To improve it, I tried the version B below, but it does not work at all.



    It will be awfull especially when the same part of code is large.



    So, to sumarize, is there a better way of handling optional arguments (to be there or not) to avoid heavy duplicate code.



    documentclass{article}
    usepackage{geometry,fancyhdr,xparse}
    geometry{showframe}

    begin{document}
    pagestyle{fancy}
    fancyhf{}

    %Version A: workable %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    NewDocumentCommand{firstpage}{momm}{%
    IfNoValueTF{#2}
    {#1{%
    ifnumvalue{page}=1
    #3% content of header/footer only at the first page
    else
    #4% content of header/footer at the rest pages
    fi
    }
    }
    {#1[#2]% the only diferrence between the two branches of IfNoValueTF is, whether introducing the optional argument #2
    {%
    ifnumvalue{page}=1
    #3% content of header/footer only at the first page
    else
    #4% content of header/footer at the rest pages
    fi
    }
    }
    }%firstpage

    % Test
    firstpage{fancyhead}[c]{only at the first page}{at rest pages}
    firstpage{rhead}{r first}{r rest}
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

    % Version B: not workable %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    NewDocumentCommand{firstpageA}{momm}{%
    #1 IfNoValueTF{#2}{}{[#2]}
    ifnumvalue{page}=1
    #3% content of header/footer only at the first page
    else
    #4% content of header/footer at the rest pages
    fi
    }%firstpageA

    % Test
    firstpageA{fancyhead}[c]{only at the first page}{at rest pages}
    firstpageA{rhead}{r first}{r rest}









    share|improve this question



























      1












      1








      1








      The version A part in the following example is to define header/footer by macros from package fancyhdr.



      Though this version is workable, it's a awkward achievement because the same part of code(ifnum...) is written twice.



      Except the optional argument #2, all other code is exactly the same. To improve it, I tried the version B below, but it does not work at all.



      It will be awfull especially when the same part of code is large.



      So, to sumarize, is there a better way of handling optional arguments (to be there or not) to avoid heavy duplicate code.



      documentclass{article}
      usepackage{geometry,fancyhdr,xparse}
      geometry{showframe}

      begin{document}
      pagestyle{fancy}
      fancyhf{}

      %Version A: workable %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
      NewDocumentCommand{firstpage}{momm}{%
      IfNoValueTF{#2}
      {#1{%
      ifnumvalue{page}=1
      #3% content of header/footer only at the first page
      else
      #4% content of header/footer at the rest pages
      fi
      }
      }
      {#1[#2]% the only diferrence between the two branches of IfNoValueTF is, whether introducing the optional argument #2
      {%
      ifnumvalue{page}=1
      #3% content of header/footer only at the first page
      else
      #4% content of header/footer at the rest pages
      fi
      }
      }
      }%firstpage

      % Test
      firstpage{fancyhead}[c]{only at the first page}{at rest pages}
      firstpage{rhead}{r first}{r rest}
      %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

      % Version B: not workable %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
      NewDocumentCommand{firstpageA}{momm}{%
      #1 IfNoValueTF{#2}{}{[#2]}
      ifnumvalue{page}=1
      #3% content of header/footer only at the first page
      else
      #4% content of header/footer at the rest pages
      fi
      }%firstpageA

      % Test
      firstpageA{fancyhead}[c]{only at the first page}{at rest pages}
      firstpageA{rhead}{r first}{r rest}









      share|improve this question
















      The version A part in the following example is to define header/footer by macros from package fancyhdr.



      Though this version is workable, it's a awkward achievement because the same part of code(ifnum...) is written twice.



      Except the optional argument #2, all other code is exactly the same. To improve it, I tried the version B below, but it does not work at all.



      It will be awfull especially when the same part of code is large.



      So, to sumarize, is there a better way of handling optional arguments (to be there or not) to avoid heavy duplicate code.



      documentclass{article}
      usepackage{geometry,fancyhdr,xparse}
      geometry{showframe}

      begin{document}
      pagestyle{fancy}
      fancyhf{}

      %Version A: workable %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
      NewDocumentCommand{firstpage}{momm}{%
      IfNoValueTF{#2}
      {#1{%
      ifnumvalue{page}=1
      #3% content of header/footer only at the first page
      else
      #4% content of header/footer at the rest pages
      fi
      }
      }
      {#1[#2]% the only diferrence between the two branches of IfNoValueTF is, whether introducing the optional argument #2
      {%
      ifnumvalue{page}=1
      #3% content of header/footer only at the first page
      else
      #4% content of header/footer at the rest pages
      fi
      }
      }
      }%firstpage

      % Test
      firstpage{fancyhead}[c]{only at the first page}{at rest pages}
      firstpage{rhead}{r first}{r rest}
      %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

      % Version B: not workable %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
      NewDocumentCommand{firstpageA}{momm}{%
      #1 IfNoValueTF{#2}{}{[#2]}
      ifnumvalue{page}=1
      #3% content of header/footer only at the first page
      else
      #4% content of header/footer at the rest pages
      fi
      }%firstpageA

      % Test
      firstpageA{fancyhead}[c]{only at the first page}{at rest pages}
      firstpageA{rhead}{r first}{r rest}






      fancyhdr xparse






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 2 mins ago







      lyl

















      asked 13 mins ago









      lyllyl

      64128




      64128






















          0






          active

          oldest

          votes











          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%2f476544%2fto-be-or-not-to-be-optional-arguments-inside-defination-of-macro%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          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%2f476544%2fto-be-or-not-to-be-optional-arguments-inside-defination-of-macro%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

          A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

          Calculate evaluation metrics using cross_val_predict sklearn

          Insert data from modal to MySQL (multiple modal on website)