Use mode-* to set var require-final-newline #26
Conversation
This file contains hidden or 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
|
You are right. The adoc tutorial and the adoc doc do not impose a newline character at the end of the text. So it should be left to the users general setting. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 follows the documentation of
mode-require-final-newlinethat says the local value ofrequire-final-newlineshould be set to the value of the former (mode-require-final-newline). Another important thing to mention is that this will fix the issue / warning that occurs when using adoc-mode with ethan-wspace. This shouldn't change the behavior for any other users because the default value ofmode-require-final-newlineis true anyway.