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

typos/grammar in documentation #251

Merged
merged 17 commits into from
Nov 10, 2023
Merged

typos/grammar in documentation #251

merged 17 commits into from
Nov 10, 2023

Conversation

dragoncoder047
Copy link
Contributor

I'm a native English speaker, so I guess I'm qualified to clean up the docstrings.

Largest changes: All occurrences of "Function return ...." were changed to "Returns ...." and likewise.

Also, I noticed that the documentation for the numerical comparison functions (> and friends) was at best confusing ("monotonically nondecreasing", wat?), and possibly completely backwards, so I rewrote it to what I think is correct, and added some explainer examples.

Feel free to reject any of my changes, especially if I misunderstood what the function does :)

@jcubic
Copy link
Owner

jcubic commented Nov 10, 2023

Thanks. There was an issue (#217) and some folks fixed some grammar mistakes during last year's Hacktoberfest but it seems not everything was fixed.

The build failed so the tests didn't even run, probably something with a branch name. I will try to fix it locally and you will merge it with devel.

@dragoncoder047
Copy link
Contributor Author

I already did make (3bd529a) -- maybe that's why, there were no changes.

@jcubic
Copy link
Owner

jcubic commented Nov 10, 2023

CI/CD run make/make lint/make test.

What do you mean by no changes?

@dragoncoder047
Copy link
Contributor Author

What do you mean by no changes?

I had some github actions workflows on other repos of mine that run a build script and then git-commit the changes and push as the GHA bot. When I already built it myself in the previous commit, the git commit command failed with "no changes to commit" and exit status 1 which caused the action to say it failed.

@dragoncoder047
Copy link
Contributor Author

Also, the last few lines of the action log that failed say:

sed -e "s/{{VER}}/1.0.0-beta.16/g" -e "s/{{BRANCH}}/`git branch | grep '^*' | sed 's/* //'`/g" -e "s/{{YEAR}}/`date +%Y`/g" \
-e "s/{{CHECKSUM}}/`cat tests/test.js tests/*.scm | md5sum | cut -d' ' -f 1`/g" -e "s/{{COMMIT}}/`git rev-parse HEAD`/g" -e "s/{{DATE}}/`date +%Y-%m-%d`/" \
-e "s/{{VER_DASH}}/`echo -n "1.0.0-beta.16" | sed "s/-/%E2%80%93/"`/g" < templates/README.md > README.md
sed: -e expression #2, char 40: unknown option to `s'
make: *** [Makefile:67: README.md] Error 1
Error: Process completed with exit code 2.

(direct link)

@jcubic
Copy link
Owner

jcubic commented Nov 10, 2023

Please merge with pr-build-fix, I've fixed build and lint errors, your lines were too long, the max is 90 characters. Also, there was one test that filed because you changed the typecheck message.

@jcubic
Copy link
Owner

jcubic commented Nov 10, 2023

This project doesn't have any GitHub actions that do commits. There are only checks that make sure that the code builds and runs.

The problem was that Makefile by default on Ubuntu uses sh that point to dash. And on my system Fedora the sh points to bash. I had this problem before on a different project.

@dragoncoder047
Copy link
Contributor Author

OK, I merged pr-build-fix into my branch. (Did you mean to do the reverse -- set pr-build-fix as the PR target?)

@jcubic
Copy link
Owner

jcubic commented Nov 10, 2023

I don't understand why there are no my commits after merge. It looks like you merged the master branch (according to commits).

@dragoncoder047
Copy link
Contributor Author

Whoops, not sure why it didn't fetch all commits. Merged it all now.

@dragoncoder047
Copy link
Contributor Author

sed is still borking it.

@jcubic
Copy link
Owner

jcubic commented Nov 10, 2023

Ok I solved the issue, the problem was that the branch in PR on GitHub have a slash. The branch name is dragoncoder047/lips and my sed command choked on slash when extracting the branch name and putting it into another sed command.

@jcubic jcubic merged commit 8226ba4 into jcubic:devel Nov 10, 2023
1 of 2 checks passed
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