Reputation
2,365
Top tag
Next privilege 2,500 Rep.
Create tag synonyms
Badges
12 37
Impact
~399k people reached

2h
awarded  Popular Question
5h
revised How can I redefine the description list to pass an arg to redefined items that contain TikZ nodes?
adjusted baseline of node
5h
comment How can I redefine the description list to pass an arg to redefined items that contain TikZ nodes?
This answer seems to uses a similar redefinition of \makelabel in this answer tex.stackexchange.com/a/55989/13552 I only added this comment for the purpose of creating relationships between questions.
6h
comment How can I redefine the description list to pass an arg to redefined items that contain TikZ nodes?
That is pretty darn close to what I am after (like 95%) without doing what I expected (I was hoping to get into the nitty gritty definitions of description lists and items such that I could add keys to description lists and pass their values to nodes within items). I will keep this question open for awhile longer to see what happens, but this is definitely a wonderful answer that I would gladly accept. Thanks! So clean!
6h
comment How can I redefine the description list to pass an arg to redefined items that contain TikZ nodes?
Yes you did understand the concept. I can do it this way, but this makes making lists a verbose experience :) I was hoping to wrap up most of the work in a new definition of the description lists. (to make it clear what i mean: before={\renewcommand\makelabel[1]{\tmark{listc\theitemcounter}\bfseries##1}} is really a bunch of code to put in the body for each list that I would like to avoid.)
6h
revised How can I redefine the description list to pass an arg to redefined items that contain TikZ nodes?
added lists tag
6h
revised How can I redefine the description list to pass an arg to redefined items that contain TikZ nodes?
added 129 characters in body
6h
revised How can I redefine the description list to pass an arg to redefined items that contain TikZ nodes?
added 233 characters in body
6h
asked How can I redefine the description list to pass an arg to redefined items that contain TikZ nodes?
9h
reviewed Approve How to insert a # via \immediate\write18 within a macro
Aug
31
accepted Why can you not skip lines in document when providing optional environment parameters with xparse?
Aug
31
comment Why can you not skip lines in document when providing optional environment parameters with xparse?
@egreg Would you consider making your comment an answer so that I can close this question? When you have time...
Aug
25
comment How can I apply a regex (l3regex) on items in a sequence? [LaTeX3]?
@egreg Why are you so fast to answer these things? I think you have a chip inplant or 6th sense that alerts you upon new stackexchange posts. Thanks :) Another thing: does \cs_set_eq:NN \__macmadness_action:n #1 just convert the inputted csname/"action" into a LaTeX3 csname/action? \__macmadness_action:n is then called by \use:n?
Aug
25
comment How can I apply a regex (l3regex) on items in a sequence? [LaTeX3]?
@egreg Why do you set the last list item to a temp variable and remove it from the list without using it? \seq_pop_right:cN { l_macmadness_list_#1_seq } \l_tmpa_tl Does this have something to do with reading a file? Is the last item useless?
Aug
24
comment Why can you not skip lines in document when providing optional environment parameters with xparse?
@egreg Ok, that makes sense. My use of trailing arguments is to create an environment that will go at the beginning of every document that contains certain required metadata that when not provided, show up in the document in nice bright letters for all to see (demonstrating that this info is indeed missing). parameters: <privacylevel> <target group> <purpose> I thought it would be better to let the parameters trail, because two of those mentioned contain paragraphs. It was purely a readability issue (in the code).
Aug
24
revised Why can you not skip lines in document when providing optional environment parameters with xparse?
added 31 characters in body
Aug
24
asked Why can you not skip lines in document when providing optional environment parameters with xparse?
Aug
20
accepted How can I force all text to continue to the next line when using style=nextline in description lists with enumitem?
Aug
20
comment How can I force all text to continue to the next line when using style=nextline in description lists with enumitem?
Exactly the same indentation as the default description list with style=nextline enabled. More importantly, I think the ability to control indentation is important and should not be sacrificed.
Aug
20
comment How can I force all text to continue to the next line when using style=nextline in description lists with enumitem?
Thanks. Actually I thought about that, but it is not aesthetically pleasing. +1 for working solution though! Maybe I will end up going for this option if I cannot find a better solution.