Skip to content

Commit

Permalink
Merge branch 'develop' into lab-review-01
Browse files Browse the repository at this point in the history
  • Loading branch information
Ulrike Fischer committed May 25, 2023
2 parents 6788a79 + 1f171b2 commit d58932c
Show file tree
Hide file tree
Showing 103 changed files with 1,955 additions and 226 deletions.
2 changes: 1 addition & 1 deletion base/README.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
The LaTeX kernel
================

Release 2023-06-01 pre-release 2
Release 2023-06-01 pre-release 3

Overview
--------
Expand Down
6 changes: 6 additions & 0 deletions base/changes.txt
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,17 @@ It is provided for convenience only. It therefore makes no claims to
completeness or accuracy and it contains some references to files that
are not part of the distribution.
================================================================================

2023-05-22 Joseph Wright <Joseph.Wright@latex-project.org>

* usrguide.tex
Ensure url package is always loaded

2023-05-21 Phelype Oleinik <phelype.oleinik@latex-project.org>

* lthooks.dtx, ltcmdhooks.dtx:
Add support for accessing arguments in 'cmd' hooks.

2023-05-19 Joseph Wright <Joseph.Wright@latex-project.org>

* usrguide.tex (section Creating document commands and environments)
Expand Down
33 changes: 27 additions & 6 deletions base/doc/ltnews37.tex
Original file line number Diff line number Diff line change
Expand Up @@ -254,6 +254,27 @@ \subsection{Extending hooks to take arguments}
were also added. The complete documentation can be found in the
\pkg{lthooks} documentation \cite{37:lthooks-doc}.

\subsubsection{Generic \texttt{cmd} hooks with arguments}

Along with the possibility to pass arguments to a regular hook as
discussed above, generic \hook{cmd} hooks now can access the arguments
of the command they are patched into using the interface described in
the previous section.

For example, if you were to add some code to the \cs{title} command
using hooks, you could access the actual title given in the argument.
For example, to write the title of the document in the terminal you
could use:
\begin{verbatim}
\AddToHookWithArguments{cmd/title/before}
{\typeout{Document title: #1}}
\end{verbatim}

As with regular hooks, code added to a \hook{cmd} hook using
\cs{AddToHook} will not be able to access the command's arguments. This
means that, as with regular hooks, this change is completely backwards
compatible, so previous usages of \hook{cmd} hooks will work exactly as
they did before.

\subsection{Providing copy and show functions for environments}

Expand Down Expand Up @@ -391,9 +412,9 @@ \section{Code improvements}

\subsection{Performance in checking file existence}

The additon of hooks, etc., to file operations had a side-effect in that
The addition of hooks, etc., to file operations had a side-effect in that
multiple checks were made that the file existed. In larger documents using
lots of files, these filesystem operations caused non-trivial performance
lots of files, these file system operations caused non-trivial performance
impact. We now cache the existence of files, such that these repeated filesystem
calls are avoided.

Expand Down Expand Up @@ -466,7 +487,7 @@ \subsection{New key for \env{filecontents}}
that redirects the overwriting warning to the transcript file. We
think that some record of the action is still required to help with
debugging, thus it is not completely silenced. The warning that
nothing gets written, because the file aready exists (and the
nothing gets written, because the file already exists (and the
\texttt{force} key was not used), is not altered and still shows up on
the terminal.
%
Expand Down Expand Up @@ -544,7 +565,7 @@ \subsection{A fix for \cs{hspace}}
for example, \pkg{wrapfig} in that special situation).
%
This got fixed with the 2022-11 PL1 hotfix, so was already corrected in
the previous release, but only now documented in a newletter.
the previous release, but only now documented in the newsletter.
%
\githubissue{967}
Expand Down Expand Up @@ -651,7 +672,7 @@ \subsection{Displaying the exact release dates for \LaTeX{}}
In some situations it is necessary to find out the exact release dates
for older version of the \LaTeX{} format, for example, when you need
to use different code in a package depending on the availablilty of a
to use different code in a package depending on the availability of a
certain feature and you therefore want to use
\cs{IfFormatAtLeastTF}\texttt\{\meta{date}\texttt\} or the
rather horrible construction \verb/\@ifl@t@r\fmtversion{/\meta{date}\texttt\},
Expand Down Expand Up @@ -713,7 +734,7 @@ \subsection{Fresh from the press: \enquote{The \LaTeX{} Companion, third edition
To cover what we thought worth describing today, the book nearly
doubled in size. The print edition is therefore produced as a
two-volume set and sold as a bundle. Both volumes come as hardcover
two-volume set and sold as a bundle. Both volumes come as hard-cover
with ribbons to easily mark pages in the book.
To give you an idea of what is covered in the third edition you can
Expand Down

0 comments on commit d58932c

Please sign in to comment.