No verify on save #18
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Sometimes I use files that contains snippets of Ruby code but it's not a valid Ruby script as a whole. However I want to have Ruby syntax highlighting.
Since I've mapped the "Validate and Save" command to
Cmd-Sin my Textmate, I was having parse error notifications constantly when saving such files, with a carret jump to the offending line.So I've added an exit clause when a special comment is found on the first line :
no-verify.It's inspired by the Git flag
--no-verifyto bypass hooks.It shouldn't really conflict with the encoding magic comment since it's intended to be used in invalid Ruby files.