Recording the inputs of a command and producing a list of them later onParse and execute the next word as a command?How keep a running list of strings and then process them one at a timeHow to implement the macros style with mixed chars and floats in a csv file?Make a command to mark a text and class them for text analyzeWrite a macro with command, , and in argumentHow to make a list of used custom macroshow to expand some macros in latex fileUsing comma separated list input to call appropriate commandsuppress single macro from style fileProtecting blocks of text and commands, not just one command, from expansion

How do I set the Verbatim font (or the mono font) to bold by default?

How can I offer a test ride while selling a bike?

Applicants clearly not having the skills they advertise

What caused the tendency for conservatives to not support climate change regulations?

The deliberate use of misleading terminology

Have powerful mythological heroes ever run away or been deeply afraid?

Is there a way to save this session?

Are there regional foods in Westeros?

If a massive object like Jupiter flew past the Earth how close would it need to come to pull people off of the surface?

How can a single Member of the House block a Congressional bill?

Can you use a concentration spell while using Mantle of Majesty?

What is a simple, physical situation where complex numbers emerge naturally?

Order by does not work as I expect

How does increase in volume change the speed of reaction in production of NO2?

Can The Malloreon be read without first reading The Belgariad?

If Sweden was to magically float away, at what altitude would it be visible from the southern hemisphere?

Does a component pouch automatically contain components?

Select * from View takes 4 minutes

Are there mythical creatures in the world of Game of Thrones?

Can a helicopter mask itself from Radar?

Asking bank to reduce APR instead of increasing credit limit

Is there an evolutionary advantage to having two heads?

Bringing Food from Hometown for Out-of-Town Interview?

Joist hangers to use for rough cut 2x8 (2 3/4" x 8 3/4")?



Recording the inputs of a command and producing a list of them later on


Parse and execute the next word as a command?How keep a running list of strings and then process them one at a timeHow to implement the macros style with mixed chars and floats in a csv file?Make a command to mark a text and class them for text analyzeWrite a macro with command, , and in argumentHow to make a list of used custom macroshow to expand some macros in latex fileUsing comma separated list input to call appropriate commandsuppress single macro from style fileProtecting blocks of text and commands, not just one command, from expansion













4















I have some macros I use a lot, mostly just for my digital note keeping. Because of the nature of these macros, I could use a specific versions of these. For example I mention some file names throughout a document such as workdocument which assigns them a specific url, and I would like to have a list of these files at the end of the document which I can just use to copy paste into some unix terminal tool. I could parse the file with a programming language to get these, but with multiple includes it isn't something I prefer.



The contents of these commands aren't references as one would semantically understand it, so I would like to avoid using bibtex.



If this can be accomplished with a feature that only exists in any of lualatex/xelatex/pdflatex, that is fine by me.



My tex file, in the simplest sense, looks like the following:



documentclass[english]scrartcl

newcommand*thingofnote[1]#1 % Somehow add the input to an 'array' to be printed at the end as well?
begindocument

sectionSection A

A thing of note is thingofnotex, while another thing of note is thingofnotey.

sectionSection B

One must not forget about thingofnotez.

sectionAll The Things

% Here, create a list of all the things of note previously included in the document.
% Even this output would be acceptable, as long as it is not done manually:
% xyz

enddocument


In the real document there are more commands and multiple includes.



This produces,
In simplest terms, the file I have



I would like to produce a version of,
The file I would rather have



Thanks in advance.










share|improve this question

















  • 1





    See chapter 15 of the KOMA documentation which shows how to make new lists of things. The tocloft package can do this too.

    – Alan Munn
    8 hours ago
















4















I have some macros I use a lot, mostly just for my digital note keeping. Because of the nature of these macros, I could use a specific versions of these. For example I mention some file names throughout a document such as workdocument which assigns them a specific url, and I would like to have a list of these files at the end of the document which I can just use to copy paste into some unix terminal tool. I could parse the file with a programming language to get these, but with multiple includes it isn't something I prefer.



The contents of these commands aren't references as one would semantically understand it, so I would like to avoid using bibtex.



If this can be accomplished with a feature that only exists in any of lualatex/xelatex/pdflatex, that is fine by me.



My tex file, in the simplest sense, looks like the following:



documentclass[english]scrartcl

newcommand*thingofnote[1]#1 % Somehow add the input to an 'array' to be printed at the end as well?
begindocument

sectionSection A

A thing of note is thingofnotex, while another thing of note is thingofnotey.

sectionSection B

One must not forget about thingofnotez.

sectionAll The Things

% Here, create a list of all the things of note previously included in the document.
% Even this output would be acceptable, as long as it is not done manually:
% xyz

enddocument


In the real document there are more commands and multiple includes.



This produces,
In simplest terms, the file I have



I would like to produce a version of,
The file I would rather have



Thanks in advance.










share|improve this question

















  • 1





    See chapter 15 of the KOMA documentation which shows how to make new lists of things. The tocloft package can do this too.

    – Alan Munn
    8 hours ago














4












4








4


0






I have some macros I use a lot, mostly just for my digital note keeping. Because of the nature of these macros, I could use a specific versions of these. For example I mention some file names throughout a document such as workdocument which assigns them a specific url, and I would like to have a list of these files at the end of the document which I can just use to copy paste into some unix terminal tool. I could parse the file with a programming language to get these, but with multiple includes it isn't something I prefer.



The contents of these commands aren't references as one would semantically understand it, so I would like to avoid using bibtex.



If this can be accomplished with a feature that only exists in any of lualatex/xelatex/pdflatex, that is fine by me.



My tex file, in the simplest sense, looks like the following:



documentclass[english]scrartcl

newcommand*thingofnote[1]#1 % Somehow add the input to an 'array' to be printed at the end as well?
begindocument

sectionSection A

A thing of note is thingofnotex, while another thing of note is thingofnotey.

sectionSection B

One must not forget about thingofnotez.

sectionAll The Things

% Here, create a list of all the things of note previously included in the document.
% Even this output would be acceptable, as long as it is not done manually:
% xyz

enddocument


In the real document there are more commands and multiple includes.



This produces,
In simplest terms, the file I have



I would like to produce a version of,
The file I would rather have



Thanks in advance.










share|improve this question














I have some macros I use a lot, mostly just for my digital note keeping. Because of the nature of these macros, I could use a specific versions of these. For example I mention some file names throughout a document such as workdocument which assigns them a specific url, and I would like to have a list of these files at the end of the document which I can just use to copy paste into some unix terminal tool. I could parse the file with a programming language to get these, but with multiple includes it isn't something I prefer.



The contents of these commands aren't references as one would semantically understand it, so I would like to avoid using bibtex.



If this can be accomplished with a feature that only exists in any of lualatex/xelatex/pdflatex, that is fine by me.



My tex file, in the simplest sense, looks like the following:



documentclass[english]scrartcl

newcommand*thingofnote[1]#1 % Somehow add the input to an 'array' to be printed at the end as well?
begindocument

sectionSection A

A thing of note is thingofnotex, while another thing of note is thingofnotey.

sectionSection B

One must not forget about thingofnotez.

sectionAll The Things

% Here, create a list of all the things of note previously included in the document.
% Even this output would be acceptable, as long as it is not done manually:
% xyz

enddocument


In the real document there are more commands and multiple includes.



This produces,
In simplest terms, the file I have



I would like to produce a version of,
The file I would rather have



Thanks in advance.







macros






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 8 hours ago









LaceyLacey

353




353







  • 1





    See chapter 15 of the KOMA documentation which shows how to make new lists of things. The tocloft package can do this too.

    – Alan Munn
    8 hours ago













  • 1





    See chapter 15 of the KOMA documentation which shows how to make new lists of things. The tocloft package can do this too.

    – Alan Munn
    8 hours ago








1




1





See chapter 15 of the KOMA documentation which shows how to make new lists of things. The tocloft package can do this too.

– Alan Munn
8 hours ago






See chapter 15 of the KOMA documentation which shows how to make new lists of things. The tocloft package can do this too.

– Alan Munn
8 hours ago











2 Answers
2






active

oldest

votes


















5














For Dr. Seuss lovers, this approach will actually create macros thing1 and thing2! (in csname form, of course)



documentclass[english]scrartcl
usepackagepgffor
newcounterthings
newcommand*thingofnote[1]#1%
stepcounterthingsexpandaftergdefcsname thingthethingsendcsname#1
newcommandlistthings%
beginenumerate
foreachz in1,...,thethingsitem csname thingzendcsname
endenumerate

begindocument

sectionSection A

A thing of note is thingofnotex, while another thing of note is thingofnotey.

sectionSection B

One must not forget about thingofnotez.

sectionAll The Things

listthings

enddocument


enter image description here



The approach can be generalized to multi-paragraph things of note as follows:



documentclass[english]scrartcl
usepackagepgffor
newcounterthings
newcommandthingofnote[1]#1%
stepcounterthingsexpandaftergdefcsname thingthethingsendcsname#1
newcommandlistthings%
beginenumerate
foreachz in1,...,thethingsitem csname thingzendcsname
endenumerate

begindocument

sectionSection A

A thing of note is thingofnotex

and new paragraph of more x, while another thing of note is thingofnotey.

sectionSection B

One must not forget about thingofnotez.

sectionAll The Things

listthings

enddocument


enter image description here






share|improve this answer




















  • 1





    Just nitpicking: You don't need to use longgdef for thing<n> (of course it doesn't hurt either :-) because the par will be in the definition. Non-long commands only trap par when they appear in the argument. Also the expandafter before long can be dropped; TeX will remember prefixes until the first unexpandable token is found, so expandafter is ok.

    – Phelype Oleinik
    6 hours ago






  • 1





    @PhelypeOleinik Thank you for that wisdom. I learned something new!

    – Steven B. Segletes
    6 hours ago












  • Thanks for the answers everyone. I am going to mark this as the answer since I have to choose one of them, but I probably will use similar code to both of these solutions in my documents over time. This seems easier to expand upon, although the etoolbox solution looks simpler for documents that I was already using the etoolbox package on. Thanks again, these help a lot.

    – Lacey
    3 hours ago



















3














Using etoolbox's docsvlist:



enter image description here



documentclass[english]scrartcl
usepackageetoolbox

newcommandmylistofstuff
newcommand*thingofnote[1]%
gapptomylistofstuff,#1% Add to list
#1% write on paper
begindocument

sectionSection A

A thing of note is thingofnotex, while another thing of note is thingofnotey.

sectionSection B

One must not forget about thingofnotez.

sectionAll The Things

beginenumerate
defdo#1item #1
expandafterdocsvlistexpandaftermylistofstuff
endenumerate

enddocument





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%2f493247%2frecording-the-inputs-of-a-command-and-producing-a-list-of-them-later-on%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    5














    For Dr. Seuss lovers, this approach will actually create macros thing1 and thing2! (in csname form, of course)



    documentclass[english]scrartcl
    usepackagepgffor
    newcounterthings
    newcommand*thingofnote[1]#1%
    stepcounterthingsexpandaftergdefcsname thingthethingsendcsname#1
    newcommandlistthings%
    beginenumerate
    foreachz in1,...,thethingsitem csname thingzendcsname
    endenumerate

    begindocument

    sectionSection A

    A thing of note is thingofnotex, while another thing of note is thingofnotey.

    sectionSection B

    One must not forget about thingofnotez.

    sectionAll The Things

    listthings

    enddocument


    enter image description here



    The approach can be generalized to multi-paragraph things of note as follows:



    documentclass[english]scrartcl
    usepackagepgffor
    newcounterthings
    newcommandthingofnote[1]#1%
    stepcounterthingsexpandaftergdefcsname thingthethingsendcsname#1
    newcommandlistthings%
    beginenumerate
    foreachz in1,...,thethingsitem csname thingzendcsname
    endenumerate

    begindocument

    sectionSection A

    A thing of note is thingofnotex

    and new paragraph of more x, while another thing of note is thingofnotey.

    sectionSection B

    One must not forget about thingofnotez.

    sectionAll The Things

    listthings

    enddocument


    enter image description here






    share|improve this answer




















    • 1





      Just nitpicking: You don't need to use longgdef for thing<n> (of course it doesn't hurt either :-) because the par will be in the definition. Non-long commands only trap par when they appear in the argument. Also the expandafter before long can be dropped; TeX will remember prefixes until the first unexpandable token is found, so expandafter is ok.

      – Phelype Oleinik
      6 hours ago






    • 1





      @PhelypeOleinik Thank you for that wisdom. I learned something new!

      – Steven B. Segletes
      6 hours ago












    • Thanks for the answers everyone. I am going to mark this as the answer since I have to choose one of them, but I probably will use similar code to both of these solutions in my documents over time. This seems easier to expand upon, although the etoolbox solution looks simpler for documents that I was already using the etoolbox package on. Thanks again, these help a lot.

      – Lacey
      3 hours ago
















    5














    For Dr. Seuss lovers, this approach will actually create macros thing1 and thing2! (in csname form, of course)



    documentclass[english]scrartcl
    usepackagepgffor
    newcounterthings
    newcommand*thingofnote[1]#1%
    stepcounterthingsexpandaftergdefcsname thingthethingsendcsname#1
    newcommandlistthings%
    beginenumerate
    foreachz in1,...,thethingsitem csname thingzendcsname
    endenumerate

    begindocument

    sectionSection A

    A thing of note is thingofnotex, while another thing of note is thingofnotey.

    sectionSection B

    One must not forget about thingofnotez.

    sectionAll The Things

    listthings

    enddocument


    enter image description here



    The approach can be generalized to multi-paragraph things of note as follows:



    documentclass[english]scrartcl
    usepackagepgffor
    newcounterthings
    newcommandthingofnote[1]#1%
    stepcounterthingsexpandaftergdefcsname thingthethingsendcsname#1
    newcommandlistthings%
    beginenumerate
    foreachz in1,...,thethingsitem csname thingzendcsname
    endenumerate

    begindocument

    sectionSection A

    A thing of note is thingofnotex

    and new paragraph of more x, while another thing of note is thingofnotey.

    sectionSection B

    One must not forget about thingofnotez.

    sectionAll The Things

    listthings

    enddocument


    enter image description here






    share|improve this answer




















    • 1





      Just nitpicking: You don't need to use longgdef for thing<n> (of course it doesn't hurt either :-) because the par will be in the definition. Non-long commands only trap par when they appear in the argument. Also the expandafter before long can be dropped; TeX will remember prefixes until the first unexpandable token is found, so expandafter is ok.

      – Phelype Oleinik
      6 hours ago






    • 1





      @PhelypeOleinik Thank you for that wisdom. I learned something new!

      – Steven B. Segletes
      6 hours ago












    • Thanks for the answers everyone. I am going to mark this as the answer since I have to choose one of them, but I probably will use similar code to both of these solutions in my documents over time. This seems easier to expand upon, although the etoolbox solution looks simpler for documents that I was already using the etoolbox package on. Thanks again, these help a lot.

      – Lacey
      3 hours ago














    5












    5








    5







    For Dr. Seuss lovers, this approach will actually create macros thing1 and thing2! (in csname form, of course)



    documentclass[english]scrartcl
    usepackagepgffor
    newcounterthings
    newcommand*thingofnote[1]#1%
    stepcounterthingsexpandaftergdefcsname thingthethingsendcsname#1
    newcommandlistthings%
    beginenumerate
    foreachz in1,...,thethingsitem csname thingzendcsname
    endenumerate

    begindocument

    sectionSection A

    A thing of note is thingofnotex, while another thing of note is thingofnotey.

    sectionSection B

    One must not forget about thingofnotez.

    sectionAll The Things

    listthings

    enddocument


    enter image description here



    The approach can be generalized to multi-paragraph things of note as follows:



    documentclass[english]scrartcl
    usepackagepgffor
    newcounterthings
    newcommandthingofnote[1]#1%
    stepcounterthingsexpandaftergdefcsname thingthethingsendcsname#1
    newcommandlistthings%
    beginenumerate
    foreachz in1,...,thethingsitem csname thingzendcsname
    endenumerate

    begindocument

    sectionSection A

    A thing of note is thingofnotex

    and new paragraph of more x, while another thing of note is thingofnotey.

    sectionSection B

    One must not forget about thingofnotez.

    sectionAll The Things

    listthings

    enddocument


    enter image description here






    share|improve this answer















    For Dr. Seuss lovers, this approach will actually create macros thing1 and thing2! (in csname form, of course)



    documentclass[english]scrartcl
    usepackagepgffor
    newcounterthings
    newcommand*thingofnote[1]#1%
    stepcounterthingsexpandaftergdefcsname thingthethingsendcsname#1
    newcommandlistthings%
    beginenumerate
    foreachz in1,...,thethingsitem csname thingzendcsname
    endenumerate

    begindocument

    sectionSection A

    A thing of note is thingofnotex, while another thing of note is thingofnotey.

    sectionSection B

    One must not forget about thingofnotez.

    sectionAll The Things

    listthings

    enddocument


    enter image description here



    The approach can be generalized to multi-paragraph things of note as follows:



    documentclass[english]scrartcl
    usepackagepgffor
    newcounterthings
    newcommandthingofnote[1]#1%
    stepcounterthingsexpandaftergdefcsname thingthethingsendcsname#1
    newcommandlistthings%
    beginenumerate
    foreachz in1,...,thethingsitem csname thingzendcsname
    endenumerate

    begindocument

    sectionSection A

    A thing of note is thingofnotex

    and new paragraph of more x, while another thing of note is thingofnotey.

    sectionSection B

    One must not forget about thingofnotez.

    sectionAll The Things

    listthings

    enddocument


    enter image description here







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 6 hours ago

























    answered 8 hours ago









    Steven B. SegletesSteven B. Segletes

    166k9210427




    166k9210427







    • 1





      Just nitpicking: You don't need to use longgdef for thing<n> (of course it doesn't hurt either :-) because the par will be in the definition. Non-long commands only trap par when they appear in the argument. Also the expandafter before long can be dropped; TeX will remember prefixes until the first unexpandable token is found, so expandafter is ok.

      – Phelype Oleinik
      6 hours ago






    • 1





      @PhelypeOleinik Thank you for that wisdom. I learned something new!

      – Steven B. Segletes
      6 hours ago












    • Thanks for the answers everyone. I am going to mark this as the answer since I have to choose one of them, but I probably will use similar code to both of these solutions in my documents over time. This seems easier to expand upon, although the etoolbox solution looks simpler for documents that I was already using the etoolbox package on. Thanks again, these help a lot.

      – Lacey
      3 hours ago













    • 1





      Just nitpicking: You don't need to use longgdef for thing<n> (of course it doesn't hurt either :-) because the par will be in the definition. Non-long commands only trap par when they appear in the argument. Also the expandafter before long can be dropped; TeX will remember prefixes until the first unexpandable token is found, so expandafter is ok.

      – Phelype Oleinik
      6 hours ago






    • 1





      @PhelypeOleinik Thank you for that wisdom. I learned something new!

      – Steven B. Segletes
      6 hours ago












    • Thanks for the answers everyone. I am going to mark this as the answer since I have to choose one of them, but I probably will use similar code to both of these solutions in my documents over time. This seems easier to expand upon, although the etoolbox solution looks simpler for documents that I was already using the etoolbox package on. Thanks again, these help a lot.

      – Lacey
      3 hours ago








    1




    1





    Just nitpicking: You don't need to use longgdef for thing<n> (of course it doesn't hurt either :-) because the par will be in the definition. Non-long commands only trap par when they appear in the argument. Also the expandafter before long can be dropped; TeX will remember prefixes until the first unexpandable token is found, so expandafter is ok.

    – Phelype Oleinik
    6 hours ago





    Just nitpicking: You don't need to use longgdef for thing<n> (of course it doesn't hurt either :-) because the par will be in the definition. Non-long commands only trap par when they appear in the argument. Also the expandafter before long can be dropped; TeX will remember prefixes until the first unexpandable token is found, so expandafter is ok.

    – Phelype Oleinik
    6 hours ago




    1




    1





    @PhelypeOleinik Thank you for that wisdom. I learned something new!

    – Steven B. Segletes
    6 hours ago






    @PhelypeOleinik Thank you for that wisdom. I learned something new!

    – Steven B. Segletes
    6 hours ago














    Thanks for the answers everyone. I am going to mark this as the answer since I have to choose one of them, but I probably will use similar code to both of these solutions in my documents over time. This seems easier to expand upon, although the etoolbox solution looks simpler for documents that I was already using the etoolbox package on. Thanks again, these help a lot.

    – Lacey
    3 hours ago






    Thanks for the answers everyone. I am going to mark this as the answer since I have to choose one of them, but I probably will use similar code to both of these solutions in my documents over time. This seems easier to expand upon, although the etoolbox solution looks simpler for documents that I was already using the etoolbox package on. Thanks again, these help a lot.

    – Lacey
    3 hours ago












    3














    Using etoolbox's docsvlist:



    enter image description here



    documentclass[english]scrartcl
    usepackageetoolbox

    newcommandmylistofstuff
    newcommand*thingofnote[1]%
    gapptomylistofstuff,#1% Add to list
    #1% write on paper
    begindocument

    sectionSection A

    A thing of note is thingofnotex, while another thing of note is thingofnotey.

    sectionSection B

    One must not forget about thingofnotez.

    sectionAll The Things

    beginenumerate
    defdo#1item #1
    expandafterdocsvlistexpandaftermylistofstuff
    endenumerate

    enddocument





    share|improve this answer



























      3














      Using etoolbox's docsvlist:



      enter image description here



      documentclass[english]scrartcl
      usepackageetoolbox

      newcommandmylistofstuff
      newcommand*thingofnote[1]%
      gapptomylistofstuff,#1% Add to list
      #1% write on paper
      begindocument

      sectionSection A

      A thing of note is thingofnotex, while another thing of note is thingofnotey.

      sectionSection B

      One must not forget about thingofnotez.

      sectionAll The Things

      beginenumerate
      defdo#1item #1
      expandafterdocsvlistexpandaftermylistofstuff
      endenumerate

      enddocument





      share|improve this answer

























        3












        3








        3







        Using etoolbox's docsvlist:



        enter image description here



        documentclass[english]scrartcl
        usepackageetoolbox

        newcommandmylistofstuff
        newcommand*thingofnote[1]%
        gapptomylistofstuff,#1% Add to list
        #1% write on paper
        begindocument

        sectionSection A

        A thing of note is thingofnotex, while another thing of note is thingofnotey.

        sectionSection B

        One must not forget about thingofnotez.

        sectionAll The Things

        beginenumerate
        defdo#1item #1
        expandafterdocsvlistexpandaftermylistofstuff
        endenumerate

        enddocument





        share|improve this answer













        Using etoolbox's docsvlist:



        enter image description here



        documentclass[english]scrartcl
        usepackageetoolbox

        newcommandmylistofstuff
        newcommand*thingofnote[1]%
        gapptomylistofstuff,#1% Add to list
        #1% write on paper
        begindocument

        sectionSection A

        A thing of note is thingofnotex, while another thing of note is thingofnotey.

        sectionSection B

        One must not forget about thingofnotez.

        sectionAll The Things

        beginenumerate
        defdo#1item #1
        expandafterdocsvlistexpandaftermylistofstuff
        endenumerate

        enddocument






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 8 hours ago









        LaTeXerLaTeXer

        839




        839



























            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%2f493247%2frecording-the-inputs-of-a-command-and-producing-a-list-of-them-later-on%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

            Canceling a color specificationRandomly assigning color to Graphics3D objects?Default color for Filling in Mathematica 9Coloring specific elements of sets with a prime modified order in an array plotHow to pick a color differing significantly from the colors already in a given color list?Detection of the text colorColor numbers based on their valueCan color schemes for use with ColorData include opacity specification?My dynamic color schemes

            Invision Community Contents History See also References External links Navigation menuProprietaryinvisioncommunity.comIPS Community ForumsIPS Community Forumsthis blog entry"License Changes, IP.Board 3.4, and the Future""Interview -- Matt Mecham of Ibforums""CEO Invision Power Board, Matt Mecham Is a Liar, Thief!"IPB License Explanation 1.3, 1.3.1, 2.0, and 2.1ArchivedSecurity Fixes, Updates And Enhancements For IPB 1.3.1Archived"New Demo Accounts - Invision Power Services"the original"New Default Skin"the original"Invision Power Board 3.0.0 and Applications Released"the original"Archived copy"the original"Perpetual licenses being done away with""Release Notes - Invision Power Services""Introducing: IPS Community Suite 4!"Invision Community Release Notes

            199年 目錄 大件事 到箇年出世嗰人 到箇年死嗰人 節慶、風俗習慣 導覽選單