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

Sync updated documentation from jparse #1018

Merged
merged 4 commits into from
Nov 5, 2024
Merged

Conversation

xexyl
Copy link
Contributor

@xexyl xexyl commented Nov 5, 2024

Comments were also updated in some of the jparse files as well as fixes in the jparse_bug_report.sh script (problems that occurred due to the carry-over from this repo to its own repo).

A man page was also updated with another example.

Comments were also updated in some of the jparse files as well as fixes
in the jparse_bug_report.sh script (problems that occurred due to the
carry-over from this repo to its own repo).

A man page was also updated with another example.
@xexyl
Copy link
Contributor Author

xexyl commented Nov 5, 2024

This seems like something worth syncing. I have something else to ponder but that's for another day (if anything comes of it).

It is no longer just an IOCCC json parser so that has been removed.
Copy link
Contributor

@lcn2 lcn2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🐈

@lcn2 lcn2 merged commit dceb9ed into ioccc-src:master Nov 5, 2024
3 checks passed
@xexyl
Copy link
Contributor Author

xexyl commented Nov 6, 2024

🐈

What an adorable kitty needs is an adorable doggy friend! 🐶

@xexyl xexyl deleted the doc-jparse branch November 6, 2024 20:09
@xexyl
Copy link
Contributor Author

xexyl commented Nov 6, 2024

Anyway I renamed the file again today .. as jparse_util_README.md could suggest it's the jparse(1) tool itself that's documented when it's more than one utility. I can worry about syncing it another time, or you can if you wish. Might have other documentation updates too but not today.

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

Successfully merging this pull request may close these issues.

2 participants