Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

\disable@package@load ready to be used by third-party classes? #1292

Closed
muzimuzhi opened this issue Mar 11, 2024 · 1 comment
Closed

\disable@package@load ready to be used by third-party classes? #1292

muzimuzhi opened this issue Mar 11, 2024 · 1 comment
Assignees
Labels
bug (improve documentation) nothing really wrong but documentation could be better category base (latex)

Comments

@muzimuzhi
Copy link
Contributor

Brief outline of the enhancement

LaTeX2e generally cannot add new features without an extreme amount of care to accommodate backwards compatibility. Please do not be offended if your request is closed for being infeasible.

Added in 2020-10-01 and documented in texdoc ltfilehook-doc, the functionality provided by \disable@package@load{<package>}{<alternate-code>} looks very useful to third-party classes, see for example T-F-S/tcolorbox#273 (comment).

From their current doc, it seems to me \disable@package@load and \reenable@package@load are ready to be used by third-party classes, since it's a little boring that only standard classes can make use of them.
image

But considering they are documented in section titled "Internal interfaces for LaTeX", I open this issue to ask the current status of their usability.

@FrankMittelbach FrankMittelbach added category base (latex) fixed in dev Fixed in development branch, not in stable release bug (improve documentation) nothing really wrong but documentation could be better labels Mar 13, 2024
FrankMittelbach added a commit that referenced this issue Mar 13, 2024
also fixed type in in change entry for amsmath
@FrankMittelbach
Copy link
Member

The heading is a bit unfortunate. The intention was to distinguish this from the file hooks which have applications for users while these commands arereally for the kernel, classes or packages (and therefore also have @ in their names). And, of course, they have only few use cases and should not be used to disable or replace something unnecessarily. But yes they can be used.

I have updated the documentation to better reflect this.

@FrankMittelbach FrankMittelbach self-assigned this Mar 13, 2024
davidcarlisle pushed a commit that referenced this issue Mar 14, 2024
also fixed type in in change entry for amsmath
davidcarlisle added a commit that referenced this issue Mar 15, 2024
* initial commit of l3sys-query package

* missing section and other comments raised by @FrankMittelbach

* add examples section

* editorial rewording, and code comments

* updated documentation for #1292
also fixed type in in change entry for amsmath

* Update l3backend, l3kernel and xparse to 2024-03-14

* Load TeX Gyre Termes by filename

We seem to have a luaotfload cache issue otherwise.

* Update luaotfload and lualibs

* .tlg changes

* Revert "Load TeX Gyre Termes by filename"

This reverts commit 03f8a34.

May or may not work ... lets see!

* Update unicode-data to 2023-09-18

* Unicode file details show in .tlg files

* Update lua-uni-alogs

* Update graphics-def to 2022-09-22

* Drop local copy of KOMA

* thus

---------

Co-authored-by: Frank Mittelbach <frank.mittelbach@latex-project.org>
Co-authored-by: Joseph Wright <joseph@texdev.net>
@FrankMittelbach FrankMittelbach removed the fixed in dev Fixed in development branch, not in stable release label Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug (improve documentation) nothing really wrong but documentation could be better category base (latex)
Projects
Development

No branches or pull requests

2 participants