enumitem: Understanding the usage of asterisk and exclamation mark in setting the different lengthsHow to set the different fontsize according to different levels in an enumitem list in beamer?Using pgfkeys to switch between “enumerate” and “enumerate*” when using the enumitem package with the package option “inline”"No effect when use the command setlist with enumitem and outlines packagesSetting the enumi counter under custom enumeration with enumitemSetting the enumi counter under parametrized enumitemDifferent output of ref and cref in lists with enumitem+cleverefprintglossaries hangs in the presence of both enumitem and beamerarticleUsing enumitem, how can I remove the label and the indent from an individual item in a list?Different spacing for same enumerate in and out the tcolorbox
Is ideal gas incompressible?
What does it mean for something to be strictly less than epsilon for an arbitrary epsilon?
Why is 'additive' EQ more difficult to use than 'subtractive'?
Is it normal to "extract a paper" from a master thesis?
Is there a word for pant sleeves?
Can the Conjure Barrage spell stack with the Disarming Attack or Trip Attack Battle Master maneuvers?
Is there an idiom that means that you are in a very strong negotiation position in a negotiation?
What is the winged creature on the back of the Mordenkainen's Tome of Foes book?
How did the Allies achieve air superiority on Sicily?
Does attacking (or having a rider attack) cancel Charge/Pounce-like abilities?
csname in newenviroment
How to make Flex Markers appear in Logic Pro X?
Meaning of "half-crown enclosure"
Why is a weak base more able to deprotonate a strong acid than a weak acid?
Which are the advantages/disadvantages of includestandalone?
why "American-born", not "America-born"?
Writing "hahaha" versus describing the laugh
What technology is there beyond RAID for disk cluster in a server
Can a UK national work as a paid shop assistant in the USA?
Can someone get a spouse off a deed that never lived together and was incarcerated?
How to safely discharge oneself
Variable does not Exist: CaseTrigger
Why does the -OH group in β-naphthol direct the incoming diazonium salt towards the ortho position?
Island Perimeter
enumitem: Understanding the usage of asterisk and exclamation mark in setting the different lengths
How to set the different fontsize according to different levels in an enumitem list in beamer?Using pgfkeys to switch between “enumerate” and “enumerate*” when using the enumitem package with the package option “inline”"No effect when use the command setlist with enumitem and outlines packagesSetting the enumi counter under custom enumeration with enumitemSetting the enumi counter under parametrized enumitemDifferent output of ref and cref in lists with enumitem+cleverefprintglossaries hangs in the presence of both enumitem and beamerarticleUsing enumitem, how can I remove the label and the indent from an individual item in a list?Different spacing for same enumerate in and out the tcolorbox
In enumitem manual, I can't find a clear explanation of the difference between the usage of exclamation mark and asterisk for leftmargin, itemindent, labelsep, labelwidth, and labelindent.
For example, what is the difference between setting labelsep=*

and labelsep=!?

documentclassarticle
usepackageenumitem
newcommandlitem[1]itembfseries#1.space
begindocument
beginenumerate[label=(alph*),labelsep=!]
litemTerm one First term description.
litemTerm two Second term description.
endenumerate
enddocument
enumitem
add a comment |
In enumitem manual, I can't find a clear explanation of the difference between the usage of exclamation mark and asterisk for leftmargin, itemindent, labelsep, labelwidth, and labelindent.
For example, what is the difference between setting labelsep=*

and labelsep=!?

documentclassarticle
usepackageenumitem
newcommandlitem[1]itembfseries#1.space
begindocument
beginenumerate[label=(alph*),labelsep=!]
litemTerm one First term description.
litemTerm two Second term description.
endenumerate
enddocument
enumitem
Could you explain what was left unclear by the explanation on page 7 of the manual? I found it rather comprehensive.
– schtandard
May 14 at 21:17
2
@schtandard If it's very clear to you, post an answer that doesn't quote the text of the documentation, but instead explains it in another way (perhaps with some examples.) This would be a really useful answer, I suspect.
– Alan Munn
May 14 at 21:21
add a comment |
In enumitem manual, I can't find a clear explanation of the difference between the usage of exclamation mark and asterisk for leftmargin, itemindent, labelsep, labelwidth, and labelindent.
For example, what is the difference between setting labelsep=*

and labelsep=!?

documentclassarticle
usepackageenumitem
newcommandlitem[1]itembfseries#1.space
begindocument
beginenumerate[label=(alph*),labelsep=!]
litemTerm one First term description.
litemTerm two Second term description.
endenumerate
enddocument
enumitem
In enumitem manual, I can't find a clear explanation of the difference between the usage of exclamation mark and asterisk for leftmargin, itemindent, labelsep, labelwidth, and labelindent.
For example, what is the difference between setting labelsep=*

and labelsep=!?

documentclassarticle
usepackageenumitem
newcommandlitem[1]itembfseries#1.space
begindocument
beginenumerate[label=(alph*),labelsep=!]
litemTerm one First term description.
litemTerm two Second term description.
endenumerate
enddocument
enumitem
enumitem
asked May 14 at 21:06
DiaaDiaa
2,98811857
2,98811857
Could you explain what was left unclear by the explanation on page 7 of the manual? I found it rather comprehensive.
– schtandard
May 14 at 21:17
2
@schtandard If it's very clear to you, post an answer that doesn't quote the text of the documentation, but instead explains it in another way (perhaps with some examples.) This would be a really useful answer, I suspect.
– Alan Munn
May 14 at 21:21
add a comment |
Could you explain what was left unclear by the explanation on page 7 of the manual? I found it rather comprehensive.
– schtandard
May 14 at 21:17
2
@schtandard If it's very clear to you, post an answer that doesn't quote the text of the documentation, but instead explains it in another way (perhaps with some examples.) This would be a really useful answer, I suspect.
– Alan Munn
May 14 at 21:21
Could you explain what was left unclear by the explanation on page 7 of the manual? I found it rather comprehensive.
– schtandard
May 14 at 21:17
Could you explain what was left unclear by the explanation on page 7 of the manual? I found it rather comprehensive.
– schtandard
May 14 at 21:17
2
2
@schtandard If it's very clear to you, post an answer that doesn't quote the text of the documentation, but instead explains it in another way (perhaps with some examples.) This would be a really useful answer, I suspect.
– Alan Munn
May 14 at 21:21
@schtandard If it's very clear to you, post an answer that doesn't quote the text of the documentation, but instead explains it in another way (perhaps with some examples.) This would be a really useful answer, I suspect.
– Alan Munn
May 14 at 21:21
add a comment |
1 Answer
1
active
oldest
votes
As explained in the enumitem documentation, the horizontal spacing in lists is composed of the parameters leftmargin, itemindent, labelsep, labelwidth and labelindent as follows:

That is to say:
The values obey the relation
leftmargin = labelindent + labelwidth + labelsep - itemindentThe right edge of the
itemlabel will be indented bylabelindent + labelwidth.- The first line of the Text of the
itemwill be indented byleftmargin + itemindent. - Subsequent lines will be indented by
leftmargin.
As you can see, there are five parameters but they are not all independent. Given any four of them you can calculate the fifth, which is where the ! and * values to these options come in.
Why have this redundancy at all? Well, in standard LaTeX, the parameter labelindent does not exist; it is introduced by enumitem. The author of the package felt that it might be useful to be able to directly set the indentation of the list label instead of having to calculate the other values manually in order to achieve the desired indentation.
By default, the new parameter labelindent is always calculated from the others. If you want to directly set labelindent, you will have to tell enumitem which parameter it should calculate instead. That is what the ! value is for.
* does exactly the same thing, but it also first sets labelwidth. This is useful because the right edge of the label is indented by 'labelindent + labelwidth', so the left edge of the label will only be indented by exactly labelindent, if the width of the label is actually labelwidth. enumitem tries to guess the width of the widest possible label by measuring the width of the label with value
0 iflabelis set usingarabic*,
viii iflabelis set usingroman*,
m iflabelis set usingalph*and- similarly for the uppercase versions.
So, if you set label=(alpha*), enumitem will measure the width of (m) and set labelwidth to this value. You can change this behavior using the widest option.
Note that this means that labelwidth=! and labelwidth=* do exactly the same thing.
Okay, so let's have a look at an example. enumitem acknowledges that the behavior of these values may be confusing and provides DrawEnumitemLabel to visualize the current values, which I will use below. It
[...] draws 4 rules from top to bottom, leftmargin (thin), labelindent (thick if positive, thin if negative), labelwidth (thick) and labelsep (thick if positive, thin if negative). If 0, a rule is not shown.
documentclassarticle
usepackageenumitem
parindent=0pt
newcommand*printvalue[1]textttstring #1 : the #1
begindocument
% set some defaults:
setlist
label=(alph*),
leftmargin=50pt,
itemindent=10pt,
labelsep=5pt,
labelwidth=25pt,
labelindent=10pt,
By default, my definition of verb|labelindent| is just ignored and it is calculated from the other values:
beginenumerate
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
I can change that using the verb|!| value.
For example, I can instead calculate verb|labelsep| from the other values:
beginenumerate[labelindent=10pt, labelsep=!]
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
The verb|*| value does exactly the same, only it also set the value of verb|labelwidth| first.
It tries to guess the widest possible label (textsl0 for verb|arabic*|, textslviii for verb|roman*|, textslm for verb|alph*|):
beginenumerate[labelindent=10pt, labelsep=*]
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
enddocument

1
+1 Great answer!
– Alan Munn
May 14 at 22:50
1
This encyclopedic and informative answer is what I am looking for. Many thanks for your great explanation.
– Diaa
May 14 at 23:09
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/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
);
);
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%2f490872%2fenumitem-understanding-the-usage-of-asterisk-and-exclamation-mark-in-setting-th%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
As explained in the enumitem documentation, the horizontal spacing in lists is composed of the parameters leftmargin, itemindent, labelsep, labelwidth and labelindent as follows:

That is to say:
The values obey the relation
leftmargin = labelindent + labelwidth + labelsep - itemindentThe right edge of the
itemlabel will be indented bylabelindent + labelwidth.- The first line of the Text of the
itemwill be indented byleftmargin + itemindent. - Subsequent lines will be indented by
leftmargin.
As you can see, there are five parameters but they are not all independent. Given any four of them you can calculate the fifth, which is where the ! and * values to these options come in.
Why have this redundancy at all? Well, in standard LaTeX, the parameter labelindent does not exist; it is introduced by enumitem. The author of the package felt that it might be useful to be able to directly set the indentation of the list label instead of having to calculate the other values manually in order to achieve the desired indentation.
By default, the new parameter labelindent is always calculated from the others. If you want to directly set labelindent, you will have to tell enumitem which parameter it should calculate instead. That is what the ! value is for.
* does exactly the same thing, but it also first sets labelwidth. This is useful because the right edge of the label is indented by 'labelindent + labelwidth', so the left edge of the label will only be indented by exactly labelindent, if the width of the label is actually labelwidth. enumitem tries to guess the width of the widest possible label by measuring the width of the label with value
0 iflabelis set usingarabic*,
viii iflabelis set usingroman*,
m iflabelis set usingalph*and- similarly for the uppercase versions.
So, if you set label=(alpha*), enumitem will measure the width of (m) and set labelwidth to this value. You can change this behavior using the widest option.
Note that this means that labelwidth=! and labelwidth=* do exactly the same thing.
Okay, so let's have a look at an example. enumitem acknowledges that the behavior of these values may be confusing and provides DrawEnumitemLabel to visualize the current values, which I will use below. It
[...] draws 4 rules from top to bottom, leftmargin (thin), labelindent (thick if positive, thin if negative), labelwidth (thick) and labelsep (thick if positive, thin if negative). If 0, a rule is not shown.
documentclassarticle
usepackageenumitem
parindent=0pt
newcommand*printvalue[1]textttstring #1 : the #1
begindocument
% set some defaults:
setlist
label=(alph*),
leftmargin=50pt,
itemindent=10pt,
labelsep=5pt,
labelwidth=25pt,
labelindent=10pt,
By default, my definition of verb|labelindent| is just ignored and it is calculated from the other values:
beginenumerate
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
I can change that using the verb|!| value.
For example, I can instead calculate verb|labelsep| from the other values:
beginenumerate[labelindent=10pt, labelsep=!]
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
The verb|*| value does exactly the same, only it also set the value of verb|labelwidth| first.
It tries to guess the widest possible label (textsl0 for verb|arabic*|, textslviii for verb|roman*|, textslm for verb|alph*|):
beginenumerate[labelindent=10pt, labelsep=*]
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
enddocument

1
+1 Great answer!
– Alan Munn
May 14 at 22:50
1
This encyclopedic and informative answer is what I am looking for. Many thanks for your great explanation.
– Diaa
May 14 at 23:09
add a comment |
As explained in the enumitem documentation, the horizontal spacing in lists is composed of the parameters leftmargin, itemindent, labelsep, labelwidth and labelindent as follows:

That is to say:
The values obey the relation
leftmargin = labelindent + labelwidth + labelsep - itemindentThe right edge of the
itemlabel will be indented bylabelindent + labelwidth.- The first line of the Text of the
itemwill be indented byleftmargin + itemindent. - Subsequent lines will be indented by
leftmargin.
As you can see, there are five parameters but they are not all independent. Given any four of them you can calculate the fifth, which is where the ! and * values to these options come in.
Why have this redundancy at all? Well, in standard LaTeX, the parameter labelindent does not exist; it is introduced by enumitem. The author of the package felt that it might be useful to be able to directly set the indentation of the list label instead of having to calculate the other values manually in order to achieve the desired indentation.
By default, the new parameter labelindent is always calculated from the others. If you want to directly set labelindent, you will have to tell enumitem which parameter it should calculate instead. That is what the ! value is for.
* does exactly the same thing, but it also first sets labelwidth. This is useful because the right edge of the label is indented by 'labelindent + labelwidth', so the left edge of the label will only be indented by exactly labelindent, if the width of the label is actually labelwidth. enumitem tries to guess the width of the widest possible label by measuring the width of the label with value
0 iflabelis set usingarabic*,
viii iflabelis set usingroman*,
m iflabelis set usingalph*and- similarly for the uppercase versions.
So, if you set label=(alpha*), enumitem will measure the width of (m) and set labelwidth to this value. You can change this behavior using the widest option.
Note that this means that labelwidth=! and labelwidth=* do exactly the same thing.
Okay, so let's have a look at an example. enumitem acknowledges that the behavior of these values may be confusing and provides DrawEnumitemLabel to visualize the current values, which I will use below. It
[...] draws 4 rules from top to bottom, leftmargin (thin), labelindent (thick if positive, thin if negative), labelwidth (thick) and labelsep (thick if positive, thin if negative). If 0, a rule is not shown.
documentclassarticle
usepackageenumitem
parindent=0pt
newcommand*printvalue[1]textttstring #1 : the #1
begindocument
% set some defaults:
setlist
label=(alph*),
leftmargin=50pt,
itemindent=10pt,
labelsep=5pt,
labelwidth=25pt,
labelindent=10pt,
By default, my definition of verb|labelindent| is just ignored and it is calculated from the other values:
beginenumerate
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
I can change that using the verb|!| value.
For example, I can instead calculate verb|labelsep| from the other values:
beginenumerate[labelindent=10pt, labelsep=!]
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
The verb|*| value does exactly the same, only it also set the value of verb|labelwidth| first.
It tries to guess the widest possible label (textsl0 for verb|arabic*|, textslviii for verb|roman*|, textslm for verb|alph*|):
beginenumerate[labelindent=10pt, labelsep=*]
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
enddocument

1
+1 Great answer!
– Alan Munn
May 14 at 22:50
1
This encyclopedic and informative answer is what I am looking for. Many thanks for your great explanation.
– Diaa
May 14 at 23:09
add a comment |
As explained in the enumitem documentation, the horizontal spacing in lists is composed of the parameters leftmargin, itemindent, labelsep, labelwidth and labelindent as follows:

That is to say:
The values obey the relation
leftmargin = labelindent + labelwidth + labelsep - itemindentThe right edge of the
itemlabel will be indented bylabelindent + labelwidth.- The first line of the Text of the
itemwill be indented byleftmargin + itemindent. - Subsequent lines will be indented by
leftmargin.
As you can see, there are five parameters but they are not all independent. Given any four of them you can calculate the fifth, which is where the ! and * values to these options come in.
Why have this redundancy at all? Well, in standard LaTeX, the parameter labelindent does not exist; it is introduced by enumitem. The author of the package felt that it might be useful to be able to directly set the indentation of the list label instead of having to calculate the other values manually in order to achieve the desired indentation.
By default, the new parameter labelindent is always calculated from the others. If you want to directly set labelindent, you will have to tell enumitem which parameter it should calculate instead. That is what the ! value is for.
* does exactly the same thing, but it also first sets labelwidth. This is useful because the right edge of the label is indented by 'labelindent + labelwidth', so the left edge of the label will only be indented by exactly labelindent, if the width of the label is actually labelwidth. enumitem tries to guess the width of the widest possible label by measuring the width of the label with value
0 iflabelis set usingarabic*,
viii iflabelis set usingroman*,
m iflabelis set usingalph*and- similarly for the uppercase versions.
So, if you set label=(alpha*), enumitem will measure the width of (m) and set labelwidth to this value. You can change this behavior using the widest option.
Note that this means that labelwidth=! and labelwidth=* do exactly the same thing.
Okay, so let's have a look at an example. enumitem acknowledges that the behavior of these values may be confusing and provides DrawEnumitemLabel to visualize the current values, which I will use below. It
[...] draws 4 rules from top to bottom, leftmargin (thin), labelindent (thick if positive, thin if negative), labelwidth (thick) and labelsep (thick if positive, thin if negative). If 0, a rule is not shown.
documentclassarticle
usepackageenumitem
parindent=0pt
newcommand*printvalue[1]textttstring #1 : the #1
begindocument
% set some defaults:
setlist
label=(alph*),
leftmargin=50pt,
itemindent=10pt,
labelsep=5pt,
labelwidth=25pt,
labelindent=10pt,
By default, my definition of verb|labelindent| is just ignored and it is calculated from the other values:
beginenumerate
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
I can change that using the verb|!| value.
For example, I can instead calculate verb|labelsep| from the other values:
beginenumerate[labelindent=10pt, labelsep=!]
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
The verb|*| value does exactly the same, only it also set the value of verb|labelwidth| first.
It tries to guess the widest possible label (textsl0 for verb|arabic*|, textslviii for verb|roman*|, textslm for verb|alph*|):
beginenumerate[labelindent=10pt, labelsep=*]
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
enddocument

As explained in the enumitem documentation, the horizontal spacing in lists is composed of the parameters leftmargin, itemindent, labelsep, labelwidth and labelindent as follows:

That is to say:
The values obey the relation
leftmargin = labelindent + labelwidth + labelsep - itemindentThe right edge of the
itemlabel will be indented bylabelindent + labelwidth.- The first line of the Text of the
itemwill be indented byleftmargin + itemindent. - Subsequent lines will be indented by
leftmargin.
As you can see, there are five parameters but they are not all independent. Given any four of them you can calculate the fifth, which is where the ! and * values to these options come in.
Why have this redundancy at all? Well, in standard LaTeX, the parameter labelindent does not exist; it is introduced by enumitem. The author of the package felt that it might be useful to be able to directly set the indentation of the list label instead of having to calculate the other values manually in order to achieve the desired indentation.
By default, the new parameter labelindent is always calculated from the others. If you want to directly set labelindent, you will have to tell enumitem which parameter it should calculate instead. That is what the ! value is for.
* does exactly the same thing, but it also first sets labelwidth. This is useful because the right edge of the label is indented by 'labelindent + labelwidth', so the left edge of the label will only be indented by exactly labelindent, if the width of the label is actually labelwidth. enumitem tries to guess the width of the widest possible label by measuring the width of the label with value
0 iflabelis set usingarabic*,
viii iflabelis set usingroman*,
m iflabelis set usingalph*and- similarly for the uppercase versions.
So, if you set label=(alpha*), enumitem will measure the width of (m) and set labelwidth to this value. You can change this behavior using the widest option.
Note that this means that labelwidth=! and labelwidth=* do exactly the same thing.
Okay, so let's have a look at an example. enumitem acknowledges that the behavior of these values may be confusing and provides DrawEnumitemLabel to visualize the current values, which I will use below. It
[...] draws 4 rules from top to bottom, leftmargin (thin), labelindent (thick if positive, thin if negative), labelwidth (thick) and labelsep (thick if positive, thin if negative). If 0, a rule is not shown.
documentclassarticle
usepackageenumitem
parindent=0pt
newcommand*printvalue[1]textttstring #1 : the #1
begindocument
% set some defaults:
setlist
label=(alph*),
leftmargin=50pt,
itemindent=10pt,
labelsep=5pt,
labelwidth=25pt,
labelindent=10pt,
By default, my definition of verb|labelindent| is just ignored and it is calculated from the other values:
beginenumerate
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
I can change that using the verb|!| value.
For example, I can instead calculate verb|labelsep| from the other values:
beginenumerate[labelindent=10pt, labelsep=!]
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
The verb|*| value does exactly the same, only it also set the value of verb|labelwidth| first.
It tries to guess the widest possible label (textsl0 for verb|arabic*|, textslviii for verb|roman*|, textslm for verb|alph*|):
beginenumerate[labelindent=10pt, labelsep=*]
DrawEnumitemLabel
item printvalueleftmargin
item printvalueitemindent
item printvaluelabelsep
item printvaluelabelwidth
item printvaluelabelindent
endenumerate
enddocument

edited May 14 at 23:00
answered May 14 at 22:24
schtandardschtandard
2,7941222
2,7941222
1
+1 Great answer!
– Alan Munn
May 14 at 22:50
1
This encyclopedic and informative answer is what I am looking for. Many thanks for your great explanation.
– Diaa
May 14 at 23:09
add a comment |
1
+1 Great answer!
– Alan Munn
May 14 at 22:50
1
This encyclopedic and informative answer is what I am looking for. Many thanks for your great explanation.
– Diaa
May 14 at 23:09
1
1
+1 Great answer!
– Alan Munn
May 14 at 22:50
+1 Great answer!
– Alan Munn
May 14 at 22:50
1
1
This encyclopedic and informative answer is what I am looking for. Many thanks for your great explanation.
– Diaa
May 14 at 23:09
This encyclopedic and informative answer is what I am looking for. Many thanks for your great explanation.
– Diaa
May 14 at 23:09
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%2f490872%2fenumitem-understanding-the-usage-of-asterisk-and-exclamation-mark-in-setting-th%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
Could you explain what was left unclear by the explanation on page 7 of the manual? I found it rather comprehensive.
– schtandard
May 14 at 21:17
2
@schtandard If it's very clear to you, post an answer that doesn't quote the text of the documentation, but instead explains it in another way (perhaps with some examples.) This would be a really useful answer, I suspect.
– Alan Munn
May 14 at 21:21