summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlineargs.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlineargs.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlineargs.html58
1 files changed, 0 insertions, 58 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlineargs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlineargs.html
deleted file mode 100644
index eccc25614ba..00000000000
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlineargs.html
+++ /dev/null
@@ -1,58 +0,0 @@
-<head>
-<title>UK TeX FAQ -- question label newlineargs</title>
-</head><body>
-<h3>Start of line goes awry</h3>
-<!-- asterisk square bracket start line -->
-<p/>This answer concerns two sorts of problems: errors of the form
-<blockquote>
-<pre>
-! Missing number, treated as zero.
-&#60;to be read again&#62;
- g
-&#60;*&#62; [grump]
-</pre>
-</blockquote><p>
-and those where a single asterisk at the start of a line mysteriously
-fails to appear in the output.
-<p/>Both problems arise because <code>\</code><code>\</code> takes optional arguments. The
-command <code>\</code><code>\*</code> means &#8220;break the line here, and inhibit page break
-following the line break&#8221;; the command <code>\</code><code>\[</code>&lt;<i>dimen</i>&gt;<code>]</code>
-means &#8220;break the line here and add &lt;<i>dimen</i>&gt; extra vertical space
-afterwards&#8221;.
-<p/>So why does <code>\</code><code>\</code> get confused by these things at the start of a
-line? It&#8217;s looking for the first non-blank thing, and in the test it
-uses ignores the end of the line in your input text.
-<p/>The solution is to enclose the stuff at the start of the new line in
-braces:
-<blockquote>
-<pre>
-{\ttfamily
- /* C-language comment\\
- {[grump]} I don't like this format\\
- {*}/
-}
-</pre>
-</blockquote><p>
-(The above text derives from an actual post to
-<i>comp.text.tex</i>; this particular bit of typesetting could
-plainly also be done using the <code>verbatim</code> environment.)
-<p/>The problem also appears in maths mode, in arrays and so on. In this
-case, large-scale bracketing of things is <em>not</em> a good idea; the
-TeX primitive <code>\</code><code>relax</code> (which does nothing except to block
-searches of this nature) may be used. From another
-<i>comp.text.tex</i> example:
-<blockquote>
-<pre>
-\begin{eqnarray}
- [a] &=& b \\
- \relax[a] &=& b
-\end{eqnarray}
-</pre>
-</blockquote><p>
-which is a usage this FAQ would not recommend, anyway: refer
-to the <a href="FAQ-eqnarray.html">reason not to use <code>eqnarray</code></a>.
-<p/>Note that the <i>amsmath</i> package modifies the behaviour of
-<code>\\</code> in maths. With <i>amsmath</i>, the <code>eqnarray</code>
-example doesn&#8217;t need any special measures.
-<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlineargs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlineargs</a>
-</body>