Lines Matching +refs:Info +refs:following +refs:node +refs:name
66 % they might have appeared in the input file name.
123 \ifx\putwordInfo\undefined \gdef\putwordInfo{Info}\fi
176 % The following is used inside several \edef's.
317 \ifpdfmakepagedest \pdfdest name{\the\pageno} xyz\fi
497 % whether the environment name matches. The \checkenv macro can also be
615 % period following counts as ending a sentence. (Idea found in latex.)
645 % @: forces normal size whitespace following.
1211 % double any backslashes. Otherwise, a name like "\node" will be
1268 % #1 is image name, #2 width (might be empty/whitespace), #3 height (ditto).
1324 \safewhatsit{\pdfdest name{\pdfdestname} xyz}%
1347 % of subentries (or empty, for subsubsections). #3 is the node text,
1348 % which might be empty if this toc entry had no corresponding node.
1352 % Generate a link to the node text if that exists; else, use the
1354 % text in the case where a section has no node, but it doesn't
1360 % Doubled backslashes in the name.
1369 \pdfoutline goto name{\pdfmkpgn{\pdfoutlinedest}}#2{\pdfoutlinetext}%
1416 % We use the node names as the destinations.
1429 % Latin 2 (0xea) gets translated to a | character. Info from
1494 \startlink attr{/Border [0 0 0]} goto name{\pdfmkpgn{#1}}
1977 % section, chapter, etc., sizes following suit. This is for the GNU
2258 % unless the following character is such as not to need one.
2817 % For double-sided printing, put current file name in lower left corner,
2818 % chapter name on inside top of right hand pages, document
2899 % to index the item name in whatever manner is desired (perhaps none).
2947 % following text (if any) will end up on the same line.
3177 % Numbers following @columnfractions are the percent of the total
3472 % #1 contains the command name as a string, e.g., `ifinfo'.
3639 % The name of an index should be no more than 2 characters long
3698 % and it is "foo", the name of the index.
3963 % (The following {} will end up in the sort string, but that's ok.)
3998 % #1 is the index name, #2 is the entry text.
4002 % #1 is name of index, #2 is stuff to put there, #3 is subentry --
4081 % The following is almost like \def\zeroskipmacro{0.0pt} except that
4117 % following glue (such as a \parskip) would be a breakpoint. For example:
4301 % The following is kludged to not output a line of dots in the index if
4444 % The following penalty ensures that the page builder is exercised
4446 % following situation:
4452 % fit on the page and has to be broken off. Without the following
4542 % We do the following ugly conditional instead of the above simple
4581 % Each @chapter defines this as the name of the chapter.
4592 \let\up=\raisesections % original BFox name
4596 \let\down=\lowersections % original BFox name
4758 % Well, we could do the following in a group, but that would break
4947 % We don't substitute the actual chapter name into \thischapter
4962 % \donoderef, because we include the current node name in the toc
4966 % For pdftex, we have to write out the node definition (aka, make
5071 % Write the node reference (= pdf destination for pdftex).
5078 % \writetocentry if there was no node). We don't want to allow that
5119 % We append the current node name (if any) and page number as additional
5121 % read this. The node name is used in the pdf outlines as the
5285 % The first argument is the chapter or section name.
5580 % This affects the following displayed environments:
5914 % following @def command, see below.
5926 % sequence (see above), and penalty of 10002 after any following
5966 % rendering the following check redundant. But we don't optimize.
5999 % @deffn category name args
6002 % @deffn category class name args
6005 % \defopon {category on}class name args
6008 % \deffngeneral {subind}category name args
6018 % @deftypefn category type name args
6021 % @deftypeop category class type name args
6024 % \deftypeopon {category on}class type name args
6027 % \deftypefngeneral {subind}category type name args
6064 % @deftp category name args
6083 % \defname, which formats the name of the @def (not the args).
6086 % #3 is the function name.
6094 % How we'll format the type name. Putting it in brackets helps
6109 % Put the type name to the right margin.
6133 #3% output function name
6142 % tt for the name. This is because literal text is sometimes needed in
6170 % if the fn name has parens in it, \boldbrax will not be in effect yet,
6285 \newtoks\macname % Macro name
6394 \else \errmessage{Macro name \the\macname\space already defined}\fi
6408 % Remove the macro name from \macrolist:
6570 node \samp{\ignorespaces#1{}}}
6572 % @node's only job in TeX is to define \lastnode, which is used in
6573 % cross-references. The @node line might or might not have commas, and
6575 % @node foo , bar , ...
6576 % We don't want such trailing spaces in the node name.
6578 \parseargdef\node{\checkenv{}\donode #1 ,\finishnodeparse}
6581 % @node Help-Cross, , , Cross-refs
6585 \let\nwnode=\node
6588 % Write a cross-reference definition for the current node. #1 is the
6606 % \setref{NAME}{SNT} defines a cross-reference point NAME (a node or an
6608 % 1) NAME-title - the current sectioning name taken from \thissection,
6609 % or the anchor name.
6636 % the node name, #2 the name of the Info cross-reference, #3 the printed
6637 % node name, #4 the name of the Info file, #5 the name of the printed
6638 % manual. All but the node name can be omitted.
6650 % No printed node name was explicitly given.
6652 % Use the node name inside the square brackets.
6665 % Otherwise just copy the Info node name.
6684 goto file{\the\filename.pdf} name{\pdfxrefdest}%
6687 goto name{\pdfmkpgn{\pdfxrefdest}}%
6698 % include an _ in the xref name, etc.
6705 % If the user specified the print name (third arg) to the ref,
6713 % if the user also gave the printed manual name (fifth arg), append
6719 % node/anchor (non-float) references.
6721 % If we use \unhbox0 and \unhbox1 to print the node names, TeX does not
6723 % not find a line break at a hyphen in a node names. Since some manuals
6724 % are best written with fairly long node names, containing hyphens, this
6725 % is a loss. Therefore, we give the text of the node name again, so it
6731 % control sequence corresponding to the node, but it has to expand
6736 % Only output a following space if the -snt ref is nonempty; for
6820 % just a \def (we prepend XR to the control sequence name to avoid
6824 {% The node name might contain 8-bit characters, which in our current
6826 % mess up the control sequence name.
6895 % in xref tags, i.e., node names. But since ^^e4 notation isn't
6897 % that is not enough: for node names that actually contain a ^
6924 % This is to support \ in node names and titles, since the \
6961 % The trailing space in the following definition for supereject is
7167 % float "here". But it seemed the best name for the future.
7212 % but we need to use it in a control sequence name.
7231 % node and anchor labels. And \xrdef uses it to construct the
7388 % but we need to use it in a control sequence name.
8542 % name cannot be active until we have parsed the command line.
8610 % file name, in case not using a pre-dumped format.