Add various comment file extensions/names #872
Merged
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
New files extensions:
- GNU linker scripts (*.ld) are commentable as a C file ("// ")
- Assembler source code (*.s) is always commentable as a Lisp file ("; ") to my knowledge
New file names:
- .empty files may be created in git-like scm having no empty folder
support. Given their name and emptiness, those files can be skipped.
- .shellcheckrc configuration files are commentable like python files
- the same for pylintrc files
Signed-off-by: Anthony Loiseau <[email protected]>
Signed-off-by: Anthony Loiseau <[email protected]>
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.
Closes #862
I couldn't force-push to the branch to solve a merge conflict. I'd manually merge it, but the main branch is protected. Git is hard.