Skip to content

Commit

Permalink
\dots is equivalent to literal ... in code blocks
Browse files Browse the repository at this point in the history
git-svn-id: https://svn.r-project.org/R/trunk@84740 00db46b3-68df-0310-9c12-caf00c1e9a41
  • Loading branch information
smeyer committed Jul 23, 2023
1 parent 0b6fdaa commit 15a721f
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions doc/manual/R-exts.texi
Original file line number Diff line number Diff line change
Expand Up @@ -7950,17 +7950,18 @@ best choice in reference manuals.) Specify the filename relative to
@section Insertions

@findex \R
Use @code{\R} for the @R{} system itself. Use @code{\dots}
Use @code{\R} for the @R{} system itself. The @code{\dots}
@findex \dots
for the dots in function argument lists @samp{@dots{}}, and
macro is a historical alternative to using literal @samp{@dots{}}
for the dots in function argument lists; use
@code{\ldots}
@findex \ldots
for ellipsis dots in ordinary text.@footnote{There is only a fine
distinction between @code{\dots} and @code{\ldots}. It is technically
incorrect to use @code{\ldots} in code blocks and @code{tools::checkRd}
will warn about this---on the other hand the current converters treat
them the same way in code blocks, and elsewhere apart from the small
distinction between the two in @LaTeX{}.} These can be followed by
distinction between the two in @LaTeX{}.} These macros can be followed by
@code{@{@}}, and should be unless followed by whitespace.

After an unescaped @samp{%}, you can put your own comments regarding the
Expand Down

0 comments on commit 15a721f

Please sign in to comment.