What is “state=start”?
up vote
6
down vote
favorite
Throughout ConTeXt's web site and documentation, there are examples that have state=start. The reference manual also has this, but it isn't clear to me what this means. In the manual, for different commands, it can take the value of start, stop, keep, none, high, empty, none, nomarking, etc.
Can someone clarify?
context
asked yesterday
Roxy
2653
New contributor
Roxy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
6
down vote
favorite
Throughout ConTeXt's web site and documentation, there are examples that have state=start. The reference manual also has this, but it isn't clear to me what this means. In the manual, for different commands, it can take the value of start, stop, keep, none, high, empty, none, nomarking, etc.
Can someone clarify?
context
asked yesterday
Roxy
2653
New contributor
Roxy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Which command are you referring to? Not all commands takestateas an argument.
– Henri Menke
yesterday
BTW, the reference manual is not a good resource, see my comments here: github.com/hmenke/context-examples/blob/master/…
– Henri Menke
yesterday
Hi @HenriMenke, I just saw it everywhere, but didn't have specific commands in mind. How aboutsetupinteraction[state=start]andsetupcolors[state=start]? Another one I saw wasdefinelogo. I assumed that since it is such a common property, it had similar meanings everywhere.
– Roxy
yesterday
setupcolors[state=start]is not necessary in MkIV. Colors are enabled by default.
– Henri Menke
yesterday
add a comment |
up vote
6
down vote
favorite
up vote
6
down vote
favorite
Throughout ConTeXt's web site and documentation, there are examples that have state=start. The reference manual also has this, but it isn't clear to me what this means. In the manual, for different commands, it can take the value of start, stop, keep, none, high, empty, none, nomarking, etc.
Can someone clarify?
context
asked yesterday
Roxy
2653
New contributor
Roxy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Throughout ConTeXt's web site and documentation, there are examples that have state=start. The reference manual also has this, but it isn't clear to me what this means. In the manual, for different commands, it can take the value of start, stop, keep, none, high, empty, none, nomarking, etc.
Can someone clarify?
context
context
asked yesterday
Roxy
2653
New contributor
Roxy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
Roxy
2653
New contributor
Roxy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited yesterday
asked yesterday
Roxy
2653
New contributor
Roxy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
Roxy
2653
asked yesterday
Roxy
2653
2653
New contributor
Roxy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Roxy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Roxy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Which command are you referring to? Not all commands takestateas an argument.
– Henri Menke
yesterday
BTW, the reference manual is not a good resource, see my comments here: github.com/hmenke/context-examples/blob/master/…
– Henri Menke
yesterday
Hi @HenriMenke, I just saw it everywhere, but didn't have specific commands in mind. How aboutsetupinteraction[state=start]andsetupcolors[state=start]? Another one I saw wasdefinelogo. I assumed that since it is such a common property, it had similar meanings everywhere.
– Roxy
yesterday
setupcolors[state=start]is not necessary in MkIV. Colors are enabled by default.
– Henri Menke
yesterday
add a comment |
1
Which command are you referring to? Not all commands takestateas an argument.
– Henri Menke
yesterday
BTW, the reference manual is not a good resource, see my comments here: github.com/hmenke/context-examples/blob/master/…
– Henri Menke
yesterday
Hi @HenriMenke, I just saw it everywhere, but didn't have specific commands in mind. How aboutsetupinteraction[state=start]andsetupcolors[state=start]? Another one I saw wasdefinelogo. I assumed that since it is such a common property, it had similar meanings everywhere.
– Roxy
yesterday
setupcolors[state=start]is not necessary in MkIV. Colors are enabled by default.
– Henri Menke
yesterday
1
1
Which command are you referring to? Not all commands take
state as an argument.– Henri Menke
yesterday
Which command are you referring to? Not all commands take
state as an argument.– Henri Menke
yesterday
BTW, the reference manual is not a good resource, see my comments here: github.com/hmenke/context-examples/blob/master/…
– Henri Menke
yesterday
BTW, the reference manual is not a good resource, see my comments here: github.com/hmenke/context-examples/blob/master/…
– Henri Menke
yesterday
Hi @HenriMenke, I just saw it everywhere, but didn't have specific commands in mind. How about
setupinteraction[state=start] and setupcolors[state=start]? Another one I saw was definelogo. I assumed that since it is such a common property, it had similar meanings everywhere.– Roxy
yesterday
Hi @HenriMenke, I just saw it everywhere, but didn't have specific commands in mind. How about
setupinteraction[state=start] and setupcolors[state=start]? Another one I saw was definelogo. I assumed that since it is such a common property, it had similar meanings everywhere.– Roxy
yesterday
setupcolors[state=start] is not necessary in MkIV. Colors are enabled by default.– Henri Menke
yesterday
setupcolors[state=start] is not necessary in MkIV. Colors are enabled by default.– Henri Menke
yesterday
add a comment |
2 Answers
2
active
oldest
votes
up vote
6
down vote
accepted
The state property is usually associated with global properties of the document. Take for example
setupinteraction[state=start]
This enables document interaction (hyperlinks). If you wanted to switch it off (maybe only temporarily), you'd use
setupinteraction[state=stop]
Searching in the ConTeXt command reference for state = gives me 46 matches. Most of them are for some internal commands or on commands where state=start is the default.
In the second part you asked about what it means for state to be something other than start or stop. I could find this for setuplayouttext where you have
state = start stop empty high none normal nomarking NAME
To be honest, I have no idea what these mean, because I have never used this command directly and there seems to be no documentation on the Wiki. There is documentation for setupheader (for which I never used the state property) which is implemented in terms of setuplayouttext.
answered yesterday
Henri Menke
67.4k7148255
add a comment |
up vote
6
down vote
Maybe as addition to Henri Menke's nice answer: There are cases where start and stop might not have the meaning you would expect, e.g. when talking about layers (from the wiki):
The available options for the "state" of a layer are:
- start: layer appears only on the current page
- stop: layer doesn't show up
- repeat: layer prints on all pages
- next: layer appears on the following page
- continue: layer appears on all pages except the first
In one of your comments you are asking about setupcolors. The wiki page tells you that it accepts four states: local, global, start and stop. In MkIV colors are enabled by default and only accept the states start and stop (see setup-en.pdf and sources).
This is just to exemplify that you should always check (and never fully trust) the documentation. If something is unclear, just ask a question, there will be people helping you :)
answered 23 hours ago
TeXnician
23.5k62984
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
6
down vote
accepted
The state property is usually associated with global properties of the document. Take for example
setupinteraction[state=start]
This enables document interaction (hyperlinks). If you wanted to switch it off (maybe only temporarily), you'd use
setupinteraction[state=stop]
Searching in the ConTeXt command reference for state = gives me 46 matches. Most of them are for some internal commands or on commands where state=start is the default.
In the second part you asked about what it means for state to be something other than start or stop. I could find this for setuplayouttext where you have
state = start stop empty high none normal nomarking NAME
To be honest, I have no idea what these mean, because I have never used this command directly and there seems to be no documentation on the Wiki. There is documentation for setupheader (for which I never used the state property) which is implemented in terms of setuplayouttext.
answered yesterday
Henri Menke
67.4k7148255
add a comment |
up vote
6
down vote
accepted
The state property is usually associated with global properties of the document. Take for example
setupinteraction[state=start]
This enables document interaction (hyperlinks). If you wanted to switch it off (maybe only temporarily), you'd use
setupinteraction[state=stop]
Searching in the ConTeXt command reference for state = gives me 46 matches. Most of them are for some internal commands or on commands where state=start is the default.
In the second part you asked about what it means for state to be something other than start or stop. I could find this for setuplayouttext where you have
state = start stop empty high none normal nomarking NAME
To be honest, I have no idea what these mean, because I have never used this command directly and there seems to be no documentation on the Wiki. There is documentation for setupheader (for which I never used the state property) which is implemented in terms of setuplayouttext.
answered yesterday
Henri Menke
67.4k7148255
add a comment |
up vote
6
down vote
accepted
up vote
6
down vote
accepted
The state property is usually associated with global properties of the document. Take for example
setupinteraction[state=start]
This enables document interaction (hyperlinks). If you wanted to switch it off (maybe only temporarily), you'd use
setupinteraction[state=stop]
Searching in the ConTeXt command reference for state = gives me 46 matches. Most of them are for some internal commands or on commands where state=start is the default.
In the second part you asked about what it means for state to be something other than start or stop. I could find this for setuplayouttext where you have
state = start stop empty high none normal nomarking NAME
To be honest, I have no idea what these mean, because I have never used this command directly and there seems to be no documentation on the Wiki. There is documentation for setupheader (for which I never used the state property) which is implemented in terms of setuplayouttext.
answered yesterday
Henri Menke
67.4k7148255
The state property is usually associated with global properties of the document. Take for example
setupinteraction[state=start]
This enables document interaction (hyperlinks). If you wanted to switch it off (maybe only temporarily), you'd use
setupinteraction[state=stop]
Searching in the ConTeXt command reference for state = gives me 46 matches. Most of them are for some internal commands or on commands where state=start is the default.
In the second part you asked about what it means for state to be something other than start or stop. I could find this for setuplayouttext where you have
state = start stop empty high none normal nomarking NAME
To be honest, I have no idea what these mean, because I have never used this command directly and there seems to be no documentation on the Wiki. There is documentation for setupheader (for which I never used the state property) which is implemented in terms of setuplayouttext.
answered yesterday
Henri Menke
67.4k7148255
answered yesterday
Henri Menke
67.4k7148255
answered yesterday
Henri Menke
67.4k7148255
answered yesterday
Henri Menke
67.4k7148255
67.4k7148255
add a comment |
add a comment |
up vote
6
down vote
Maybe as addition to Henri Menke's nice answer: There are cases where start and stop might not have the meaning you would expect, e.g. when talking about layers (from the wiki):
The available options for the "state" of a layer are:
- start: layer appears only on the current page
- stop: layer doesn't show up
- repeat: layer prints on all pages
- next: layer appears on the following page
- continue: layer appears on all pages except the first
In one of your comments you are asking about setupcolors. The wiki page tells you that it accepts four states: local, global, start and stop. In MkIV colors are enabled by default and only accept the states start and stop (see setup-en.pdf and sources).
This is just to exemplify that you should always check (and never fully trust) the documentation. If something is unclear, just ask a question, there will be people helping you :)
answered 23 hours ago
TeXnician
23.5k62984
add a comment |
up vote
6
down vote
Maybe as addition to Henri Menke's nice answer: There are cases where start and stop might not have the meaning you would expect, e.g. when talking about layers (from the wiki):
The available options for the "state" of a layer are:
- start: layer appears only on the current page
- stop: layer doesn't show up
- repeat: layer prints on all pages
- next: layer appears on the following page
- continue: layer appears on all pages except the first
In one of your comments you are asking about setupcolors. The wiki page tells you that it accepts four states: local, global, start and stop. In MkIV colors are enabled by default and only accept the states start and stop (see setup-en.pdf and sources).
This is just to exemplify that you should always check (and never fully trust) the documentation. If something is unclear, just ask a question, there will be people helping you :)
answered 23 hours ago
TeXnician
23.5k62984
add a comment |
up vote
6
down vote
up vote
6
down vote
Maybe as addition to Henri Menke's nice answer: There are cases where start and stop might not have the meaning you would expect, e.g. when talking about layers (from the wiki):
The available options for the "state" of a layer are:
- start: layer appears only on the current page
- stop: layer doesn't show up
- repeat: layer prints on all pages
- next: layer appears on the following page
- continue: layer appears on all pages except the first
In one of your comments you are asking about setupcolors. The wiki page tells you that it accepts four states: local, global, start and stop. In MkIV colors are enabled by default and only accept the states start and stop (see setup-en.pdf and sources).
This is just to exemplify that you should always check (and never fully trust) the documentation. If something is unclear, just ask a question, there will be people helping you :)
answered 23 hours ago
TeXnician
23.5k62984
Maybe as addition to Henri Menke's nice answer: There are cases where start and stop might not have the meaning you would expect, e.g. when talking about layers (from the wiki):
The available options for the "state" of a layer are:
- start: layer appears only on the current page
- stop: layer doesn't show up
- repeat: layer prints on all pages
- next: layer appears on the following page
- continue: layer appears on all pages except the first
In one of your comments you are asking about setupcolors. The wiki page tells you that it accepts four states: local, global, start and stop. In MkIV colors are enabled by default and only accept the states start and stop (see setup-en.pdf and sources).
This is just to exemplify that you should always check (and never fully trust) the documentation. If something is unclear, just ask a question, there will be people helping you :)
answered 23 hours ago
TeXnician
23.5k62984
answered 23 hours ago
TeXnician
23.5k62984
answered 23 hours ago
TeXnician
23.5k62984
answered 23 hours ago
TeXnician
23.5k62984
23.5k62984
add a comment |
add a comment |
Roxy is a new contributor. Be nice, and check out our Code of Conduct.
Roxy is a new contributor. Be nice, and check out our Code of Conduct.
Roxy is a new contributor. Be nice, and check out our Code of Conduct.
Roxy is a new contributor. Be nice, and check out our Code of Conduct.
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%2f461510%2fwhat-is-state-start%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
Which command are you referring to? Not all commands take
stateas an argument.– Henri Menke
yesterday
BTW, the reference manual is not a good resource, see my comments here: github.com/hmenke/context-examples/blob/master/…
– Henri Menke
yesterday
Hi @HenriMenke, I just saw it everywhere, but didn't have specific commands in mind. How about
setupinteraction[state=start]andsetupcolors[state=start]? Another one I saw wasdefinelogo. I assumed that since it is such a common property, it had similar meanings everywhere.– Roxy
yesterday
setupcolors[state=start]is not necessary in MkIV. Colors are enabled by default.– Henri Menke
yesterday