LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Robert Alessi <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Fri, 14 Jan 2022 08:44:06 +0100
Content-Type:
multipart/mixed
Parts/Attachments:
text/plain (333 bytes) , skeleton.dtx (3237 bytes)
Dear List,

Something happened with today's update.

Any of the -dev engines fail to compile the attached .dtx file if the
“dox” package is loaded, but I am not sure the failure is caused by
this package.

(pdf|xe|lua)latex-dev engines seem to bump into \@doc@describe which
is defined in doc-v3beta.sty.

Thank you for your help.

Best,

Robert



% \iffalse meta-comment
%
% \fi
%
% \iffalse
%<*driver>
\ProvidesFile{skeleton.dtx}
%</driver>
%<package>\NeedsTeXFormat{LaTeX2e}[2005/12/01]
%<package>\ProvidesPackage{skeleton}
%<*package>
    [2004/11/05 v1.0 .dtx skeleton file]
%</package>
%
%<*driver>
\documentclass{ltxdoc}
\usepackage{dox}
\EnableCrossrefs
\CodelineIndex
\RecordChanges
\begin{document}
  \DocInput{skeleton.dtx}
  \PrintChanges
  \PrintIndex
\end{document}
%</driver>
% \fi
%
% \CheckSum{0}
%
% \CharacterTable
% {Upper-case \A\B\C\D\E\F\G\H\I\J\K\L\M\N\O\P\Q\R\S\T\U\V\W\X\Y\Z
% Lower-case \a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z
% Digits \0\1\2\3\4\5\6\7\8\9
% Exclamation \! Double quote \" Hash (number) \#
% Dollar \$ Percent \% Ampersand \&
% Acute accent \' Left paren \( Right paren \)
% Asterisk \* Plus \+ Comma \,
% Minus \- Point \. Solidus \/
% Colon \: Semicolon \; Less than \<
% Equals \= Greater than \> Question mark \?
% Commercial at \@ Left bracket \[ Backslash \\
% Right bracket \] Circumflex \^ Underscore \_
% Grave accent \` Left brace \{ Vertical bar \|
% Right brace \} Tilde \~}
%
%
% \changes{v1.0}{2004/11/05}{Initial version}
%
% \GetFileInfo{skeleton.dtx}
%
% \DoNotIndex{\newcommand,\newenvironment}
%
%
% \title{The \textsf{skeleton} package\thanks{This document
% corresponds to \textsf{skeleton}~\fileversion, dated \filedate.}}
% \author{Scott Pakin \\ \[log in to unmask]
%
% \maketitle
%
% \section{Introduction}
%
% Put text here.
%
% \section{Usage}
%
% Put text here.
%
% \DescribeMacro{\dummyMacro}
% This macro does nothing.\index{doing nothing|usage} It is merely an
% example. If this were a real macro, you would put a paragraph here
% describing what the macro is supposed to do, what its mandatory and
% optional arguments are, and so forth.
%
% \DescribeEnv{dummyEnv}
% This environment does nothing. It is merely an example.
% If this were a real environment, you would put a paragraph here
% describing what the environment is supposed to do, what its
% mandatory and optional arguments are, and so forth.
%
% \StopEventually{}
%
% \section{Implementation}
%
% \begin{macro}{\dummyMacro}
% This is a dummy macro. If it did anything, we'd describe its
% implementation here.
% \begin{macrocode}
\newcommand{\dummyMacro}{}
% \end{macrocode}
% \end{macro}
%
% \begin{environment}{dummyEnv}
% This is a dummy environment. If it did anything, we'd describe its
% implementation here.
% \begin{macrocode}
\newenvironment{dummyEnv}{%
}{%
% \end{macrocode}
% \changes{v1.0a}{2004/11/05}{Added a spurious change log entry to
% show what a change \emph{within} an environment definition looks
% like.}
% Don't use |%| to introduce a code comment within a |macrocode|
% environment. Instead, you should typeset all of your comments with
% \LaTeX---doing so gives much prettier results. For comments within a
% macro/environment body, just do an |\end{macrocode}|, include some
% commentary, and do another |\begin{macrocode}|. It's that simple.
% \begin{macrocode}
}
% \end{macrocode}
% \end{environment}
%
% \Finale
\endinput


ATOM RSS1 RSS2