Home | History | Annotate | Download | only in build-aux

Lines Matching refs:Will

17 % This texinfo.tex file is distributed in the hope that it will be
74 % Save some plain tex macros whose names we will redefine.
322 % Do this outside of the \shipout so @code etc. will be expanded in
583 % at the beginning of a line will start with \penalty -- and
726 % There is an extremely small chance that TeX will actually break the
729 % almost-but-not-quite fill up a page, TeX will have a hard time doing
1047 % Open the new aux file. TeX will close it automatically at exit.
1108 % double any backslashes. Otherwise, a name like "\node" will be
1264 % #1 is the section text, which is what will be displayed in the
1376 % If we don't expand the argument now, \skipspaces will get
2218 % Markup style infrastructure. \defmarkupstylesetup\INITMACRO will
2512 % will therefore expand the active definition of _, which is us
2521 % An additional complication: the above will allow breaks after, e.g.,
3146 % hopefully nobody will notice/care.
3248 % in effect the toc pages will come out with page numbers.
3366 % @evenfooting will not be used by itself.
3541 % what follows is an environment such as @example, there will be no
3552 % following text (if any) will end up on the same line.
3662 % \nobreak will be last on the list, and \sectionheading will have
3664 % parskip, or the item text will crash with the heading. On the
3694 % (We will always have one token, because of the test we just made.
3779 % @multitable ... @end multitable will make as many columns as desired.
3780 % Contents of each column will wrap at width given in preamble. Width
3784 % Table can continue over pages but will only break between lines.
3805 % ie, @tab@tab@tab will produce two empty columns.
3807 % @item, @tab do not need to be on their own lines, but it will not hurt
3823 % They will wrap at the width determined by the template.
3824 % @item@tab@tab This will be in third column.
3952 % This preamble sets up a generic column definition, which will
3954 % \vtop will set a single line and will also let text wrap and
3964 % we will add a \leftskip of \multitablecolspace to all columns after
3967 % If a template has been used, we will add \multitablecolspace
3970 % If the user has set preamble in terms of percent of \hsize we will
3972 % will keep entries from bumping into each other. Table will start at
3973 % left margin and final column will justify at right margin.
3978 % The first column will be indented with the surrounding text.
3983 % we will advance \hsize by \multitablecolspace.
3986 % In either case we will make \leftskip=\multitablecolspace:
4199 % it will fail (although perhaps we could fix that with sufficient work
4415 % this will be simpler.
4443 % that will dutifully get written to the index (or wherever).
4662 % (The following {} will end up in the sort string, but that's ok.)
4755 % so it will be output as is; and it will print as backslash.
4781 % \write or \pdfdest will make \lastskip zero. The result is that
4786 % will have extra space inserted, because the \medbreak in the
5025 % there are no page numbers. The next person who breaks this will be
5090 % output routine. Generally, \partialpage will be empty when this
5091 % runs and this will be a no-op. See the indexspread.tex test case.
5145 % box0 will be the left-hand column, box2 the right.
5173 % penalty the page builder will not be exercised until \eject
5176 % double-column page will be processed with \balancecolumns, which
5177 % is wrong: The two columns will go to the main vertical list, with
5184 % \balancecolumns below; \onepageout will try to fit the two columns
5198 % though, there will be another page break right after this \output
5201 % definition right away. (We hope \balancecolumns will never be
5629 % Because \domark is called before \chapoddpage, the filler page will
5730 % after \pchapsepmacro, or the headline will change too soon.
5918 % Interline glue will be inserted when the vbox is completed.
5919 % That glue will be a valid breakpoint for the page, since it'll be
5943 % or the negative glue will cause weirdly wrong output, typically
5963 % arguments for the \{chap,sec,...}entry macros which will eventually
6241 % But \@ or @@ will get a plain @ character.
6306 % start of the next paragraph will insert \parskip.
6326 % \nonarrowing is a flag. If "set", @lisp etc don't narrow margins; it will
6540 \hbadness=10000 % Last line will usually be underfull, so turn off
6548 \hbadness=10000 % Last line will usually be underfull, so turn off
6632 % @set txicodequotebacktick will not have effect on @verb and
6798 \defunpenalty=10003 % Will keep this @deffn together with the
7080 % arguments will be output next, if any.
7115 % if the fn name has parens in it, \boldbrax will not be in effect yet,
7339 % \anythingelse will almost certainly be an error of some kind.
7446 % argument N value and then \edef the body (nothing else will expand because of
7677 % \xdef is used so that macro definitions will survive the file
7856 \safewhatsit{\writexrdef{pg}{\folio}}% will be written later, at \shipout
7994 % empty discretionaries after hyphens, which means that it will not
8049 % in a monospaced font). Hopefully it will never happen in practice.
8425 % We will only complain once about lack of epsf.tex.
8435 \errmessage{epsf.tex not found, images will be ignored}%
8464 % Usually we'll have text after the image which will insert
8476 % want to start a paragraph, which will create a hsize-width box and
8508 % this float will not be numbered and cannot be referred to.
8514 % will somehow specify the positions allowed to float to (here, top, bottom).
8705 % #1 is (maybe) the \floatmagic string. If so, #2 will be the
8746 % Figures without xref labels will not be included in the list (since
9724 % if we don't reset these, they will remain at "1 true in" of
10056 @c don't make ` and ' active, @code will not get them as active chars.