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

undefined page references in ltfilehook-code and ltshipout-code #1214

Open
mbertucci47 opened this issue Dec 19, 2023 · 2 comments · May be fixed by #1325
Open

undefined page references in ltfilehook-code and ltshipout-code #1214

mbertucci47 opened this issue Dec 19, 2023 · 2 comments · May be fixed by #1325

Comments

@mbertucci47
Copy link
Contributor

mbertucci47 commented Dec 19, 2023

Brief outline of the bug

This is the same as latex3/latex3#1345 but for ltfilehook-code and ltshipout-code, namely undefined page references in the sentences "These functions are documented on page ??". I think fixing it should just require adding the documented-as, no-user-doc, or deprecated options in the right places. Here's the list of where the undefined references occur.

ltfilehook-code

  • \InputIfFileExists, \@input@file@exists@with@hooks, and \unqu@tefilef@und
  • \set@curr@file and others
  • \@filehook@set@CurrentFile, \@kernel@make@file@csname, and \@set@curr@file@aux
  • \@@_set_curr_file:nNN and \@@_set_curr_file_assign:nnnNN
  • \BeforeClearDocument

ltshipout-code

  • \@kernel@after@shipout@lastpage, \@kernel@before@shipout@background, and \@kernel@after@shipout@background
  • \@abspage@last
  • \enddocument, \@kernel@after@enddocument, and \@kernel@after@enddocument@afterlastpage
  • \@expl@@@shipout@add@firstpage@material@@Nn and others
  • \ShipoutBoxHeight, \ShipoutBoxWidth, and \ShipoutBoxDepth
Copy link

This issue has been automatically marked as stale because it has not had recent activity.

@github-actions github-actions bot added the stale label Feb 18, 2024
@josephwright josephwright self-assigned this Apr 9, 2024
@josephwright josephwright removed the stale label Apr 9, 2024
@josephwright josephwright linked a pull request Apr 10, 2024 that will close this issue
@josephwright
Copy link
Member

I've just realised this is a bit more tricky than I originally realised, at least for the 'documented elsewhere' cases. They do work already in source2e, so we need to preserve that. Needs a bit more thought.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Pool (unscheduled issues)
Development

Successfully merging a pull request may close this issue.

3 participants