Lines Matching refs:control
438 % just before passing the control to \next.
1041 % FYI, plain.tex uses \\ as a temporary control sequence (why?), but
1399 \def\curfontstyle{#1}% not as a control sequence, because we are \edef'd.
1806 % Unfortunately, TeX uses one parameter (\hyphenchar) to control
3133 % effectively preventing its expansion. This is used only for control
3134 % words, not control letters, because the \space would be incorrect
3135 % for control characters, but is needed to separate the control word
3138 % For control letters, we have \definedummyletter, which omits the
3141 % These can be used both for control words that take an argument and
3311 % by, and when constructing control sequence names. It eliminates all
3312 % control sequences and just writes whatever the best ASCII sort string
3320 % We can just ignore other control letters.
3324 % Hopefully, all control words can become @asis.
3565 % (because it thinks @} is a control sequence).
3598 % Change them to control the appearance of the index.
4188 % These macros control what the section commands do, according
5435 % Make control sequences which act like normal parenthesis chars.
5440 % so TeX would otherwise complain about undefined control sequence.
5799 % line. Whatever was read is then fed to the next control sequence
6010 % control sequence corresponding to the node, but it has to expand
6099 % just a \def (we prepend XR to the control sequence name to avoid
6105 % Was that xref control sequence that we just defined for a float?
6119 % Remember this xref in the control sequence \floatlistFLOATTYPE,
6170 % argument, and \hat is not an expandable control sequence. It could
6478 % but we need to use it in a control sequence name.
6607 % The parameter is the control sequence identifying the counter we are
6631 % #1 is the control sequence we are passed; we expand into a conditional
6652 % but we need to use it in a control sequence name.
6684 % pass the control sequence. On the other hand, XR#1-pg is just the