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

Documentation #12

Open
Reissner opened this issue Sep 23, 2024 · 2 comments
Open

Documentation #12

Reissner opened this issue Sep 23, 2024 · 2 comments

Comments

@Reissner
Copy link

It would be helpful to find something on the possible errors and warnings logged into *.ilg.
A bit like section 3 of the makeindex manual from https://ctan.org/pkg/makeindex.
I am particularly interested in that because I am working on some build tool.

@t-tk
Copy link
Owner

t-tk commented Sep 23, 2024

I have not made list of warning/error messages.
I can say a short comment now.
The messages are generated at the following code ::

warning ::
I think you will find them by checking warn_printf() in *.c .
Some strings of warning messages are generated by SPRINTF prior to warn_printf() .

error ::
I think you will find error exit by checking exit(253) exit(254) exit(255) in *.c.
The error message will be issued by verb_printf() or fprintf() prior to exit().

@Reissner
Copy link
Author

Thank you for answering.. Is error always combined with exit code !=0?

I remember that makeindex prints some summary... at best, I find something upmendex and makeindex have in common.

I think, if errors, codes and also log output is specified as done for makeindex, manual section 3,
this is really realiable, more than having a look at the code,
because code is not specification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants