[latex3-commits] [git/LaTeX3-latex3-latex3] gh450: Index correctly (or do not index) some more commands (9f4b7626e)

Bruno Le Floch blflatex at gmail.com
Fri Apr 23 21:15:25 CEST 2021


Repository : https://github.com/latex3/latex3
On branch  : gh450
Link       : https://github.com/latex3/latex3/commit/9f4b7626eceb46e8071c5c1d1788f40cbd0296a0

>---------------------------------------------------------------

commit 9f4b7626eceb46e8071c5c1d1788f40cbd0296a0
Author: Bruno Le Floch <blflatex at gmail.com>
Date:   Fri Apr 23 21:15:25 2021 +0200

    Index correctly (or do not index) some more commands


>---------------------------------------------------------------

9f4b7626eceb46e8071c5c1d1788f40cbd0296a0
 l3kernel/l3fp-traps.dtx    |  2 +-
 l3kernel/l3msg.dtx         |  4 ++--
 l3kernel/l3regex.dtx       | 16 ++++++++--------
 l3kernel/l3sort.dtx        |  2 +-
 l3kernel/l3str-convert.dtx |  2 +-
 l3kernel/l3tl.dtx          |  2 +-
 6 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/l3kernel/l3fp-traps.dtx b/l3kernel/l3fp-traps.dtx
index 1f95b5d41..d4c4d8625 100644
--- a/l3kernel/l3fp-traps.dtx
+++ b/l3kernel/l3fp-traps.dtx
@@ -70,7 +70,7 @@
 %
 % \subsection{Flags}
 %
-% \begin{variable}
+% \begin{variable}[module = fp]
 %   {
 %     flag fp_invalid_operation,
 %     flag fp_division_by_zero,
diff --git a/l3kernel/l3msg.dtx b/l3kernel/l3msg.dtx
index 2ca828912..258af244b 100644
--- a/l3kernel/l3msg.dtx
+++ b/l3kernel/l3msg.dtx
@@ -2119,14 +2119,14 @@
 % \begin{macro}{\@@_expandable_error:w}
 %   In expansion only context, we cannot use the normal means of
 %   reporting errors. Instead, we feed \TeX{} an undefined control
-%   sequence, \cs{LaTeX3 error:}. It is thus interrupted, and shows
+%   sequence, \cs[module = {}]{LaTeX3 error:}. It is thus interrupted, and shows
 %   the context, which thanks to the odd-looking \cs{use:n} is
 %   \begin{verbatim}
 %     <argument> \LaTeX3 error:
 %                               The error message.
 %   \end{verbatim}
 %   In other words, \TeX{} is processing the argument of \cs{use:n},
-%   which is \cs{LaTeX3 error:} \meta{error message}.
+%   which is \cs[module = {}]{LaTeX3 error:} \meta{error message}.
 %   Then \cs{@@_expandable_error:w} cleans up. In fact, there
 %   is an extra subtlety: if the user inserts tokens for error recovery,
 %   they should be kept. Thus we also use an odd space character
diff --git a/l3kernel/l3regex.dtx b/l3kernel/l3regex.dtx
index f38a7e7d5..00e2f4a5c 100644
--- a/l3kernel/l3regex.dtx
+++ b/l3kernel/l3regex.dtx
@@ -66,7 +66,7 @@
 %   \tl_set:Nn \l_my_tl { That~cat. }
 %   \regex_replace_once:nnN { at } { is } \l_my_tl
 % \end{verbatim}
-% the token list variable \cs{l_my_tl} holds the text
+% the token list variable \cs[no-index]{l_my_tl} holds the text
 % \enquote{\texttt{This cat.}}, where the first
 % occurrence of \enquote{\texttt{at}} was replaced
 % by \enquote{\texttt{is}}. A more complicated example is
@@ -372,13 +372,13 @@
 % \begin{verbatim}
 %   \regex_extract_all:nnN { a \K . } { a123aaxyz } \l_foo_seq
 % \end{verbatim}
-% results in \cs{l_foo_seq} containing the items |{1}| and |{a}|: the
+% results in \cs[no-index]{l_foo_seq} containing the items |{1}| and |{a}|: the
 % true matches are |{a1}| and |{aa}|, but they are trimmed by the use of
 % |\K|. The |\K| command does not affect capturing groups: for instance,
 % \begin{verbatim}
 %   \regex_extract_once:nnN { (. \K c)+ \d } { acbc3 } \l_foo_seq
 % \end{verbatim}
-% results in \cs{l_foo_seq} containing the items |{c3}| and |{bc}|: the
+% results in \cs[no-index]{l_foo_seq} containing the items |{c3}| and |{bc}|: the
 % true match is |{acbc3}|, with first submatch |{bc}|, but |\K| resets
 % the beginning of the match to the last position where it appears.
 %
@@ -412,7 +412,7 @@
 %   \tl_set:Nn \l_my_tl { Hello,~world! }
 %   \regex_replace_all:nnN { ([er]?l|o) . } { (\0--\1) } \l_my_tl
 % \end{verbatim}
-% results in \cs{l_my_tl} holding |H(ell--el)(o,--o) w(or--o)(ld--l)!|
+% results in \cs[no-index]{l_my_tl} holding |H(ell--el)(o,--o) w(or--o)(ld--l)!|
 %
 % The submatches are numbered according to the order in which the
 % opening parenthesis of capturing groups appear in the regular
@@ -455,7 +455,7 @@
 %   \tl_set:Nn \l_my_tl { one , two , one , one }
 %   \regex_replace_all:nnN { [^,]+ } { \u{l_my_\0_tl} } \l_my_tl
 % \end{verbatim}
-% results in \cs{l_my_tl} holding |first,\emph{second},first,first|.
+% results in \cs[no-index]{l_my_tl} holding |first,\emph{second},first,first|.
 %
 % \section{Pre-compiling regular expressions}
 %
@@ -549,7 +549,7 @@
 %     \int_new:N \l_foo_int
 %     \regex_count:nnN { (b+|c) } { abbababcbb } \l_foo_int
 %   \end{verbatim}
-%   results in \cs{l_foo_int} taking the value $5$.
+%   results in \cs[no-index]{l_foo_int} taking the value $5$.
 % \end{function}
 %
 % \section{Submatch extraction}
@@ -577,10 +577,10 @@
 %   Then the regular expression (anchored at the start with |\A| and
 %   at the end with |\Z|) must match the whole token list. The first
 %   capturing group, |(La)?|, matches |La|, and the second capturing
-%   group, |(!*)|, matches |!!!|. Thus, |\l_foo_seq| contains as a result
+%   group, |(!*)|, matches |!!!|. Thus, \cs[no-index]{l_foo_seq} contains as a result
 %   the items |{LaTeX!!!}|, |{La}|, and |{!!!}|, and the \texttt{true}
 %   branch is left in the input stream.
-%   Note that the $n$-th item of |\l_foo_seq|, as obtained using
+%   Note that the $n$-th item of \cs[no-index]{l_foo_seq}, as obtained using
 %   \cs{seq_item:Nn}, correspond to the submatch numbered $(n-1)$ in
 %   functions such as \cs{regex_replace_once:nnN}.
 % \end{function}
diff --git a/l3kernel/l3sort.dtx b/l3kernel/l3sort.dtx
index 3c13f7232..7e0427215 100644
--- a/l3kernel/l3sort.dtx
+++ b/l3kernel/l3sort.dtx
@@ -65,7 +65,7 @@
 %         { \sort_return_same: }
 %     }
 % \end{verbatim}
-% results in \cs{l_foo_clist} holding the values
+% results in \cs[no-index]{l_foo_clist} holding the values
 % |{ -2 , 01 , +1 , 3 , 5 }| sorted in non-decreasing order.
 %
 % The code defining the comparison should call
diff --git a/l3kernel/l3str-convert.dtx b/l3kernel/l3str-convert.dtx
index 4cc29c2d2..d2d23f866 100644
--- a/l3kernel/l3str-convert.dtx
+++ b/l3kernel/l3str-convert.dtx
@@ -156,7 +156,7 @@
 %   \begin{verbatim}
 %     \str_set_convert:Nnnn \l_foo_str { Hello! } { } { utf16/hex }
 %   \end{verbatim}
-%   results in the variable \cs{l_foo_str} holding the string
+%   results in the variable \cs[no-index]{l_foo_str} holding the string
 %   \texttt{FEFF00480065006C006C006F0021}. This is obtained by
 %   converting each character in the (native) string \texttt{Hello!}  to
 %   the \textsc{utf-16} encoding, and expressing each byte as a pair of
diff --git a/l3kernel/l3tl.dtx b/l3kernel/l3tl.dtx
index c7038b08d..15c26d379 100644
--- a/l3kernel/l3tl.dtx
+++ b/l3kernel/l3tl.dtx
@@ -583,7 +583,7 @@
 %     \tl_map_tokens:Nn \l_my_tl { \prg_replicate:nn { 2 } }
 %   \end{verbatim}
 %   expands to twice each item in the \meta{tl~var}: for each item in
-%   |\l_my_tl| the function \cs{prg_replicate:nn} receives |2| and
+%   \cs[no-index]{l_my_tl} the function \cs{prg_replicate:nn} receives |2| and
 %   \meta{item} as its two arguments.  The function
 %   \cs{tl_map_inline:Nn} is typically faster but is not expandable.
 % \end{function}





More information about the latex3-commits mailing list.