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 macrosUsing 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 can an immortal member of the nobility be prevented from taking the throne?
My cat gets angry and scared at me if I stand
Can a company prevent a co-author of a paper to put his name on it?
A word/phrase means "a small amount" (of a color)
What is the basis for the custom to stand or sit by Vayivarech Dovid?
What are modes in real world?
Take-Home Examination on Ordinary Differential Equations?
Coworkers accusing me of "cheating" for working more efficiently
Does animal blood, esp. human, really have similar salinity as ocean water, and does that prove anything about evolution?
Should I be charging for the social media versions of designs?
How are astronauts in the ISS protected from electric shock?
Why is a Lockheed MC-130J Commando II creating such a loud droning sound?
Why is double encryption that's equivalent to single encryption no better than single encryption?
"Du hast es gut", small talk meaning?
How can I get a "RedLevel" instead of GrayLevel when drawing a densityplot?
Protecting Seals from Forgery
What can I use for input conversion instead of scanf?
Where are the other 36 children born the same day?
How much caffeine would there be if I reuse tea leaves in a second brewing?
Employer says they want Quality & Quantity, but only pays bonuses based on the latter
Novel about immortality being kept secret by world leaders
Parents suppressing the teaching
Mutate my DNA sequence
How can I more clearly ask people to accomodate for my autism?
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 macrosUsing comma separated list input to call appropriate commandsuppress single macro from style fileProtecting blocks of text and commands, not just one command, from expansion
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom: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,
I would like to produce a version of,
Thanks in advance.
macros
add a comment
|
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,
I would like to produce a version of,
Thanks in advance.
macros
1
See chapter 15 of the KOMA documentation which shows how to make new lists of things. Thetocloft
package can do this too.
– Alan Munn
May 29 at 17:53
add a comment
|
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,
I would like to produce a version of,
Thanks in advance.
macros
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,
I would like to produce a version of,
Thanks in advance.
macros
macros
asked May 29 at 17:50
LaceyLacey
453 bronze badges
453 bronze badges
1
See chapter 15 of the KOMA documentation which shows how to make new lists of things. Thetocloft
package can do this too.
– Alan Munn
May 29 at 17:53
add a comment
|
1
See chapter 15 of the KOMA documentation which shows how to make new lists of things. Thetocloft
package can do this too.
– Alan Munn
May 29 at 17:53
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
May 29 at 17:53
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
May 29 at 17:53
add a comment
|
2 Answers
2
active
oldest
votes
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
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
1
Just nitpicking: You don't need to uselonggdef
forthing<n>
(of course it doesn't hurt either :-) because thepar
will be in the definition. Non-long
commands only trappar
when they appear in the argument. Also theexpandafter
beforelong
can be dropped; TeX will remember prefixes until the first unexpandable token is found, soexpandafter
is ok.
– Phelype Oleinik
May 29 at 20:05
1
@PhelypeOleinik Thank you for that wisdom. I learned something new!
– Steven B. Segletes
May 29 at 20:14
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
May 29 at 23:35
add a comment
|
Using etoolbox
's docsvlist
:
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
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/4.0/"u003ecc by-sa 4.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%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
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
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
1
Just nitpicking: You don't need to uselonggdef
forthing<n>
(of course it doesn't hurt either :-) because thepar
will be in the definition. Non-long
commands only trappar
when they appear in the argument. Also theexpandafter
beforelong
can be dropped; TeX will remember prefixes until the first unexpandable token is found, soexpandafter
is ok.
– Phelype Oleinik
May 29 at 20:05
1
@PhelypeOleinik Thank you for that wisdom. I learned something new!
– Steven B. Segletes
May 29 at 20:14
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
May 29 at 23:35
add a comment
|
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
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
1
Just nitpicking: You don't need to uselonggdef
forthing<n>
(of course it doesn't hurt either :-) because thepar
will be in the definition. Non-long
commands only trappar
when they appear in the argument. Also theexpandafter
beforelong
can be dropped; TeX will remember prefixes until the first unexpandable token is found, soexpandafter
is ok.
– Phelype Oleinik
May 29 at 20:05
1
@PhelypeOleinik Thank you for that wisdom. I learned something new!
– Steven B. Segletes
May 29 at 20:14
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
May 29 at 23:35
add a comment
|
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
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
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
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
edited May 29 at 20:14
answered May 29 at 18:09
Steven B. SegletesSteven B. Segletes
172k9 gold badges218 silver badges447 bronze badges
172k9 gold badges218 silver badges447 bronze badges
1
Just nitpicking: You don't need to uselonggdef
forthing<n>
(of course it doesn't hurt either :-) because thepar
will be in the definition. Non-long
commands only trappar
when they appear in the argument. Also theexpandafter
beforelong
can be dropped; TeX will remember prefixes until the first unexpandable token is found, soexpandafter
is ok.
– Phelype Oleinik
May 29 at 20:05
1
@PhelypeOleinik Thank you for that wisdom. I learned something new!
– Steven B. Segletes
May 29 at 20:14
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
May 29 at 23:35
add a comment
|
1
Just nitpicking: You don't need to uselonggdef
forthing<n>
(of course it doesn't hurt either :-) because thepar
will be in the definition. Non-long
commands only trappar
when they appear in the argument. Also theexpandafter
beforelong
can be dropped; TeX will remember prefixes until the first unexpandable token is found, soexpandafter
is ok.
– Phelype Oleinik
May 29 at 20:05
1
@PhelypeOleinik Thank you for that wisdom. I learned something new!
– Steven B. Segletes
May 29 at 20:14
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
May 29 at 23:35
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
May 29 at 20:05
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
May 29 at 20:05
1
1
@PhelypeOleinik Thank you for that wisdom. I learned something new!
– Steven B. Segletes
May 29 at 20:14
@PhelypeOleinik Thank you for that wisdom. I learned something new!
– Steven B. Segletes
May 29 at 20:14
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
May 29 at 23:35
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
May 29 at 23:35
add a comment
|
Using etoolbox
's docsvlist
:
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
add a comment
|
Using etoolbox
's docsvlist
:
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
add a comment
|
Using etoolbox
's docsvlist
:
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
Using etoolbox
's docsvlist
:
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
answered May 29 at 18:12
LaTeXerLaTeXer
4601 silver badge11 bronze badges
4601 silver badge11 bronze badges
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%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
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
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
May 29 at 17:53