Updated Single-Include Header Download and *nix Commands #46
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
…lude header file in the Development section. Also, updated the "single-include header file" link to link to the actual header instead of the releases page. A new reference link was made for the header file in the assets section of the releases page.
… the command line" section.
faheel
requested changes
Jun 9, 2019
|
@faheel, I just wanted to say thank you for engaging with me as I've fumbled around here. You seem like a great teacher and open person. These commits are for an open source class I'm taking at university and I've never involved myself with someone else's GitHub before, so I really appreciate the effort you put in with others and the tone you take. Thanks so much! |
faheel
approved these changes
Jun 9, 2019
|
@seldonwilson, Thank YOU for engaging with open source software and contributing to it! |
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.
The single-include header file used to link to the release-link instead of the actual header file which was in the assets of the provided link. New users might get confused when they aren't taken directly to the header file or when it doesn't begin downloading when they click the link, which is what happens now. Also, if you're working on the code in the different header files, you won't have an up-to-date single-include header, so I've added the command to generate that release header as a third bullet point to the "Using the command line" section of the README.