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:
David Carlisle <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Fri, 28 Jul 2023 15:44:32 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (53 lines)
On 28/07/2023 15:28, LARONDE Thierry wrote:
> Yes. But the same engine does things differently between LaTeX
> 2022-11-01 and LaTeX 2023-06-01.

What difference are you  seeing?  If I try 2022-11-01 it acts the same
way as the current (and older) versions


  echo '\input{docstrip}' | /usr/local/texlive/2022/bin/*/latex

This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022)
(preloaded format=latex)
  restricted \write18 enabled.
**entering extended mode
LaTeX2e <2022-11-01> patch level 1
L3 programming layer <2023-02-07>
(/usr/local/texlive/2022/texmf-dist/tex/latex/base/docstrip.tex


that is: \input{docstrip} finds docstrip.tex in the path.




The only related change log (changes.txt in the latex2e/base repository)
I see for input since 2022-11-01 is


2023-06-16  Joseph Wright <[log in to unmask]>

     * ltfiles.dtx
     Allow for pipes in \input, etc.


which is the change in ltfiles.dtx marked with


% \changes{v1.2u}{2023/06/16}{Support piped input}


David






Disclaimer

The Numerical Algorithms Group Ltd is a company registered in England and Wales with company number 1249803. The registered office is: 30 St. Giles, Oxford, OX1 3LE, United Kingdom. Please see our Privacy Notice <https://www.nag.com/content/privacy-notice> for information on how we process personal data and for details of how to stop or limit communications from us.

This e-mail has been scanned for all viruses and malware by Microsoft Exchange Online (EOP)

ATOM RSS1 RSS2