-
Notifications
You must be signed in to change notification settings - Fork 7k
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
Proof LUNAR_AND_SOLAR_EPHEMERIDES_SUBROUTINES (#224) #316
Merged
wopian
merged 2 commits into
chrislgarry:master
from
dwiyatci:proof-lunar-and-solar-ephemerides-subroutines
Mar 23, 2018
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev
Previous commit
👌 Follow "triple space" rule for indentation
- Loading branch information
commit b292f92fd2e28550d83f8b32f885e0e58257e6e1
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How should we handle sentence/paragraph continuation? Should we leave it be like this or should we put a tab after the number, e.g.
1)⇥
like in https://github.com/chrislgarry/Apollo-11/blob/master/Comanche055/P76.agc? 🤔There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. I would probably use the format in that file since it is closer to how it looked in the printouts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't change those '--' in Proof P76 (#239)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@oldmud0 Hmm. If that's the argument, would it be even closer if we just put 3 spaces in the continuation? ⬇️
@keller0 🙋♂️ I'm actually also kind of undecided about that. Should we use hyphen (-) or double hyphen a.k.a. en dash (--)? Furthermore, in P76, I notice that every full stop (.) is always followed by double spaces -- is it a general rule that we have to follow here?
cc: @chrislgarry @wopian
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dwiyatci
Moving forward, lets change double hyphens to single hyphens to be consistent with the prints. @keller0 its no problem. For new PRs lets do single hyphens unless the printout says otherwise.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chrislgarry Roger that. 🙇