-
Notifications
You must be signed in to change notification settings - Fork 50
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
Update docs #359
Merged
Merged
Update docs #359
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NOTE: work in progress, do not merge yet. |
Merged
Affonso-Gui
force-pushed
the
update-docs
branch
from
April 22, 2019 04:45
11ab35f
to
6009e70
Compare
Affonso-Gui
force-pushed
the
update-docs
branch
from
April 22, 2019 04:58
6009e70
to
255c923
Compare
This was referenced Apr 24, 2019
k-okada
added a commit
to k-okada/jskeus
that referenced
this pull request
Jun 6, 2019
euslisp/EusLisp@b6a25e9#diff-95f8abe64beb6e0fc27b68349ac0cac7 in euslisp/EusLisp#359 changed definition of longdescription in EusLisp and we need to update this for jmanual.tex in jskeus too
k-okada
added a commit
to k-okada/EusLisp
that referenced
this pull request
Jun 6, 2019
euslisp@b6a25e9#diff-95f8abe64beb6e0fc27b68349ac0cac7 in euslisp#359 changed the definition of longdescription and we need to update documentation.l (which is only used in jskeus for now) too Cc: @Affonso-Gui
k-okada
added a commit
to k-okada/jskeus
that referenced
this pull request
Jun 6, 2019
euslisp/EusLisp@b6a25e9#diff-95f8abe64beb6e0fc27b68349ac0cac7 in euslisp/EusLisp#359 changed definition of longdescription in EusLisp and we need to update this for jmanual.tex in jskeus too
This was referenced Jan 31, 2020
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This ended up with more changes than I thought, but the main objectives are to:
Use lispy expressions in lambda-list doc (which should be more natural).
For example, transform
(arg1 [arg2])
into(arg1 &optional arg2)
Lint newlines and bracket positions in functions descriptions to the following form