LaTeX: Why are digits allowed in environments, but forbidden in commands?What exactly do csname and endcsname...
Important Resources for Dark Age Civilizations?
Is it inappropriate for a student to attend their mentor's dissertation defense?
What typically incentivizes a professor to change jobs to a lower ranking university?
Did Shadowfax go to Valinor?
What does "Puller Prush Person" mean?
When a company launches a new product do they "come out" with a new product or do they "come up" with a new product?
Languages that we cannot (dis)prove to be Context-Free
dbcc cleantable batch size explanation
Does detail obscure or enhance action?
"You are your self first supporter", a more proper way to say it
How does quantile regression compare to logistic regression with the variable split at the quantile?
How to format long polynomial?
Can a Cauchy sequence converge for one metric while not converging for another?
Why "Having chlorophyll without photosynthesis is actually very dangerous" and "like living with a bomb"?
Why doesn't Newton's third law mean a person bounces back to where they started when they hit the ground?
How much of data wrangling is a data scientist's job?
Malcev's paper "On a class of homogeneous spaces" in English
What defenses are there against being summoned by the Gate spell?
Perform and show arithmetic with LuaLaTeX
Does an object always see its latest internal state irrespective of thread?
Are the number of citations and number of published articles the most important criteria for a tenure promotion?
Why is Minecraft giving an OpenGL error?
Alternative to sending password over mail?
Could an aircraft fly or hover using only jets of compressed air?
LaTeX: Why are digits allowed in environments, but forbidden in commands?
What exactly do csname and endcsname do?Why are some characters not allowed in command sequencesWhy does LaTeX make a distinction between commands and environments?Do all starred commands have anything in common?Why are some characters not allowed in command sequencesSuggestions for an automatic taxonomy environmentUse a character other than the backslash for commandsWhy are LaTeX macros so inconsistent?Are end… macro names reserved in LaTeX2e?Can't use command with square brackets in matrix environmentHow to control conditional statements within new commands and environmentsCreating Commands which Make New Environments
Finding out that I can have an environment named env2
, but no command cmd2
, I read Why are some characters not allowed in command sequences, but still I wonder:
Why are digits allowed in environments, but forbidden in commands? In my understanding digits delimit command names (inherited from plain TeX), but why doesn't that restriction apply to environments? Wouldn't it have been more consistent to forbid digits in environment names as well?
macros environments
add a comment |
Finding out that I can have an environment named env2
, but no command cmd2
, I read Why are some characters not allowed in command sequences, but still I wonder:
Why are digits allowed in environments, but forbidden in commands? In my understanding digits delimit command names (inherited from plain TeX), but why doesn't that restriction apply to environments? Wouldn't it have been more consistent to forbid digits in environment names as well?
macros environments
You actually can use numbers in commands. If you doexpandafterdefcsname mycommandwithanumber123456endcsname{}
you'll define a commandmycommandwithanumber123456
. The environments are created using thecsname
...endcsname
pair, so it's fine.
– Phelype Oleinik
6 hours ago
expandafterdefcsname macro2endcsname{command output}
is valid syntax. You then must use it viacsname macro2endcsname
.
– Steven B. Segletes
6 hours ago
So the answer is "There are not forbidden, but they have to be used in a special way. Still it's recommended not to use them."?
– U. Windl
6 hours ago
add a comment |
Finding out that I can have an environment named env2
, but no command cmd2
, I read Why are some characters not allowed in command sequences, but still I wonder:
Why are digits allowed in environments, but forbidden in commands? In my understanding digits delimit command names (inherited from plain TeX), but why doesn't that restriction apply to environments? Wouldn't it have been more consistent to forbid digits in environment names as well?
macros environments
Finding out that I can have an environment named env2
, but no command cmd2
, I read Why are some characters not allowed in command sequences, but still I wonder:
Why are digits allowed in environments, but forbidden in commands? In my understanding digits delimit command names (inherited from plain TeX), but why doesn't that restriction apply to environments? Wouldn't it have been more consistent to forbid digits in environment names as well?
macros environments
macros environments
asked 7 hours ago
U. WindlU. Windl
1697
1697
You actually can use numbers in commands. If you doexpandafterdefcsname mycommandwithanumber123456endcsname{}
you'll define a commandmycommandwithanumber123456
. The environments are created using thecsname
...endcsname
pair, so it's fine.
– Phelype Oleinik
6 hours ago
expandafterdefcsname macro2endcsname{command output}
is valid syntax. You then must use it viacsname macro2endcsname
.
– Steven B. Segletes
6 hours ago
So the answer is "There are not forbidden, but they have to be used in a special way. Still it's recommended not to use them."?
– U. Windl
6 hours ago
add a comment |
You actually can use numbers in commands. If you doexpandafterdefcsname mycommandwithanumber123456endcsname{}
you'll define a commandmycommandwithanumber123456
. The environments are created using thecsname
...endcsname
pair, so it's fine.
– Phelype Oleinik
6 hours ago
expandafterdefcsname macro2endcsname{command output}
is valid syntax. You then must use it viacsname macro2endcsname
.
– Steven B. Segletes
6 hours ago
So the answer is "There are not forbidden, but they have to be used in a special way. Still it's recommended not to use them."?
– U. Windl
6 hours ago
You actually can use numbers in commands. If you do
expandafterdefcsname mycommandwithanumber123456endcsname{}
you'll define a command mycommandwithanumber123456
. The environments are created using the csname
...endcsname
pair, so it's fine.– Phelype Oleinik
6 hours ago
You actually can use numbers in commands. If you do
expandafterdefcsname mycommandwithanumber123456endcsname{}
you'll define a command mycommandwithanumber123456
. The environments are created using the csname
...endcsname
pair, so it's fine.– Phelype Oleinik
6 hours ago
expandafterdefcsname macro2endcsname{command output}
is valid syntax. You then must use it via csname macro2endcsname
.– Steven B. Segletes
6 hours ago
expandafterdefcsname macro2endcsname{command output}
is valid syntax. You then must use it via csname macro2endcsname
.– Steven B. Segletes
6 hours ago
So the answer is "There are not forbidden, but they have to be used in a special way. Still it's recommended not to use them."?
– U. Windl
6 hours ago
So the answer is "There are not forbidden, but they have to be used in a special way. Still it's recommended not to use them."?
– U. Windl
6 hours ago
add a comment |
1 Answer
1
active
oldest
votes
The restriction is in the scanner, tex's "eyes" in the texbook terminology. Any sequence of characters may be used as a command name, however after a character of catcode 0 (normally ) then tex scans the next non-letter (character of catcode other than 11) or a contiguous sequence of letters, and tokenizes it as a single csname token.
This means that foo123
normally parses as the token foo
followed by the three tokens 1
, 2
, 3
. Unless you make digits catcode 11. Similarly section*
is normally the token section
followed by the token *
.
environment names use do not require to parse the name via the escape character, (they use the csname
primitive but that's an implementation detail so begin{tabular}
accesses tabular
but begin{tabular*}
accesses the command with name tabular*
(not the two tokens that would normally be generated by parsing tabular*
).
So technically it would be quite hard to not allow digits (or other characters) in environment names, especially when latex was designed there was not the memory available to add that kind of character-by-character check.
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%2f483440%2flatex-why-are-digits-allowed-in-environments-but-forbidden-in-commands%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
The restriction is in the scanner, tex's "eyes" in the texbook terminology. Any sequence of characters may be used as a command name, however after a character of catcode 0 (normally ) then tex scans the next non-letter (character of catcode other than 11) or a contiguous sequence of letters, and tokenizes it as a single csname token.
This means that foo123
normally parses as the token foo
followed by the three tokens 1
, 2
, 3
. Unless you make digits catcode 11. Similarly section*
is normally the token section
followed by the token *
.
environment names use do not require to parse the name via the escape character, (they use the csname
primitive but that's an implementation detail so begin{tabular}
accesses tabular
but begin{tabular*}
accesses the command with name tabular*
(not the two tokens that would normally be generated by parsing tabular*
).
So technically it would be quite hard to not allow digits (or other characters) in environment names, especially when latex was designed there was not the memory available to add that kind of character-by-character check.
add a comment |
The restriction is in the scanner, tex's "eyes" in the texbook terminology. Any sequence of characters may be used as a command name, however after a character of catcode 0 (normally ) then tex scans the next non-letter (character of catcode other than 11) or a contiguous sequence of letters, and tokenizes it as a single csname token.
This means that foo123
normally parses as the token foo
followed by the three tokens 1
, 2
, 3
. Unless you make digits catcode 11. Similarly section*
is normally the token section
followed by the token *
.
environment names use do not require to parse the name via the escape character, (they use the csname
primitive but that's an implementation detail so begin{tabular}
accesses tabular
but begin{tabular*}
accesses the command with name tabular*
(not the two tokens that would normally be generated by parsing tabular*
).
So technically it would be quite hard to not allow digits (or other characters) in environment names, especially when latex was designed there was not the memory available to add that kind of character-by-character check.
add a comment |
The restriction is in the scanner, tex's "eyes" in the texbook terminology. Any sequence of characters may be used as a command name, however after a character of catcode 0 (normally ) then tex scans the next non-letter (character of catcode other than 11) or a contiguous sequence of letters, and tokenizes it as a single csname token.
This means that foo123
normally parses as the token foo
followed by the three tokens 1
, 2
, 3
. Unless you make digits catcode 11. Similarly section*
is normally the token section
followed by the token *
.
environment names use do not require to parse the name via the escape character, (they use the csname
primitive but that's an implementation detail so begin{tabular}
accesses tabular
but begin{tabular*}
accesses the command with name tabular*
(not the two tokens that would normally be generated by parsing tabular*
).
So technically it would be quite hard to not allow digits (or other characters) in environment names, especially when latex was designed there was not the memory available to add that kind of character-by-character check.
The restriction is in the scanner, tex's "eyes" in the texbook terminology. Any sequence of characters may be used as a command name, however after a character of catcode 0 (normally ) then tex scans the next non-letter (character of catcode other than 11) or a contiguous sequence of letters, and tokenizes it as a single csname token.
This means that foo123
normally parses as the token foo
followed by the three tokens 1
, 2
, 3
. Unless you make digits catcode 11. Similarly section*
is normally the token section
followed by the token *
.
environment names use do not require to parse the name via the escape character, (they use the csname
primitive but that's an implementation detail so begin{tabular}
accesses tabular
but begin{tabular*}
accesses the command with name tabular*
(not the two tokens that would normally be generated by parsing tabular*
).
So technically it would be quite hard to not allow digits (or other characters) in environment names, especially when latex was designed there was not the memory available to add that kind of character-by-character check.
edited 6 hours ago
Phelype Oleinik
24.9k54690
24.9k54690
answered 6 hours ago
David CarlisleDavid Carlisle
497k4111441892
497k4111441892
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%2f483440%2flatex-why-are-digits-allowed-in-environments-but-forbidden-in-commands%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
You actually can use numbers in commands. If you do
expandafterdefcsname mycommandwithanumber123456endcsname{}
you'll define a commandmycommandwithanumber123456
. The environments are created using thecsname
...endcsname
pair, so it's fine.– Phelype Oleinik
6 hours ago
expandafterdefcsname macro2endcsname{command output}
is valid syntax. You then must use it viacsname macro2endcsname
.– Steven B. Segletes
6 hours ago
So the answer is "There are not forbidden, but they have to be used in a special way. Still it's recommended not to use them."?
– U. Windl
6 hours ago