What is “state=start”?
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 Nov 24 '18 at 2:58
RoxyRoxy
3565
add a comment |
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 Nov 24 '18 at 2:58
RoxyRoxy
3565
1
Which command are you referring to? Not all commands takestateas an argument.
– Henri Menke
Nov 24 '18 at 3:19
BTW, the reference manual is not a good resource, see my comments here: github.com/hmenke/context-examples/blob/master/…
– Henri Menke
Nov 24 '18 at 3:36
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
Nov 24 '18 at 3:43
setupcolors[state=start]is not necessary in MkIV. Colors are enabled by default.
– Henri Menke
Nov 24 '18 at 4:35
add a comment |
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 Nov 24 '18 at 2:58
RoxyRoxy
3565
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 Nov 24 '18 at 2:58
RoxyRoxy
3565
asked Nov 24 '18 at 2:58
RoxyRoxy
3565
edited Nov 24 '18 at 3:03
Roxy
asked Nov 24 '18 at 2:58
RoxyRoxy
3565
asked Nov 24 '18 at 2:58
RoxyRoxy
3565
asked Nov 24 '18 at 2:58
RoxyRoxy
3565
3565
1
Which command are you referring to? Not all commands takestateas an argument.
– Henri Menke
Nov 24 '18 at 3:19
BTW, the reference manual is not a good resource, see my comments here: github.com/hmenke/context-examples/blob/master/…
– Henri Menke
Nov 24 '18 at 3:36
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
Nov 24 '18 at 3:43
setupcolors[state=start]is not necessary in MkIV. Colors are enabled by default.
– Henri Menke
Nov 24 '18 at 4:35
add a comment |
1
Which command are you referring to? Not all commands takestateas an argument.
– Henri Menke
Nov 24 '18 at 3:19
BTW, the reference manual is not a good resource, see my comments here: github.com/hmenke/context-examples/blob/master/…
– Henri Menke
Nov 24 '18 at 3:36
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
Nov 24 '18 at 3:43
setupcolors[state=start]is not necessary in MkIV. Colors are enabled by default.
– Henri Menke
Nov 24 '18 at 4:35
1
1
Which command are you referring to? Not all commands take
state as an argument.– Henri Menke
Nov 24 '18 at 3:19
Which command are you referring to? Not all commands take
state as an argument.– Henri Menke
Nov 24 '18 at 3:19
BTW, the reference manual is not a good resource, see my comments here: github.com/hmenke/context-examples/blob/master/…
– Henri Menke
Nov 24 '18 at 3:36
BTW, the reference manual is not a good resource, see my comments here: github.com/hmenke/context-examples/blob/master/…
– Henri Menke
Nov 24 '18 at 3:36
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
Nov 24 '18 at 3:43
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
Nov 24 '18 at 3:43
setupcolors[state=start] is not necessary in MkIV. Colors are enabled by default.– Henri Menke
Nov 24 '18 at 4:35
setupcolors[state=start] is not necessary in MkIV. Colors are enabled by default.– Henri Menke
Nov 24 '18 at 4:35
add a comment |
2 Answers
2
active
oldest
votes
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 Nov 24 '18 at 4:34
Henri MenkeHenri Menke
75.7k8165277
add a comment |
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 Nov 24 '18 at 7:54
TeXnicianTeXnician
25.2k63389
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%2f461510%2fwhat-is-state-start%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
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 Nov 24 '18 at 4:34
Henri MenkeHenri Menke
75.7k8165277
add a comment |
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 Nov 24 '18 at 4:34
Henri MenkeHenri Menke
75.7k8165277
add a comment |
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 Nov 24 '18 at 4:34
Henri MenkeHenri Menke
75.7k8165277
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 Nov 24 '18 at 4:34
Henri MenkeHenri Menke
75.7k8165277
answered Nov 24 '18 at 4:34
Henri MenkeHenri Menke
75.7k8165277
answered Nov 24 '18 at 4:34
Henri MenkeHenri Menke
75.7k8165277
answered Nov 24 '18 at 4:34
Henri MenkeHenri Menke
75.7k8165277
75.7k8165277
add a comment |
add a comment |
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 Nov 24 '18 at 7:54
TeXnicianTeXnician
25.2k63389
add a comment |
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 Nov 24 '18 at 7:54
TeXnicianTeXnician
25.2k63389
add a comment |
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 Nov 24 '18 at 7:54
TeXnicianTeXnician
25.2k63389
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 Nov 24 '18 at 7:54
TeXnicianTeXnician
25.2k63389
answered Nov 24 '18 at 7:54
TeXnicianTeXnician
25.2k63389
answered Nov 24 '18 at 7:54
TeXnicianTeXnician
25.2k63389
answered Nov 24 '18 at 7:54
TeXnicianTeXnician
25.2k63389
25.2k63389
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%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
Nov 24 '18 at 3:19
BTW, the reference manual is not a good resource, see my comments here: github.com/hmenke/context-examples/blob/master/…
– Henri Menke
Nov 24 '18 at 3:36
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
Nov 24 '18 at 3:43
setupcolors[state=start]is not necessary in MkIV. Colors are enabled by default.– Henri Menke
Nov 24 '18 at 4:35