set b:undo_indent in Vim indent plugin #88
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
See :help undo_indent for details.
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.
See :help undo_indent for details.
Go to http://gitolite.com/gitolite/index.html#contact for information on
contacting me, the mailing list, and IRC channel. Unless you are reporting
what you think is a security issue, I prefer you send to the mailing list,
not to me directly.
Please DO NOT send messages via github's "issues" system, linkedin
comments/discussion, stackoverflow questions, google+, and any other Web 3.0
"coolness". (The issues system does have an email interface, but it is not a
substitute for email. I can't cc anyone else when I want to, for instance.
Well I can, but any response the original requester then makes using the
website will not get cc-d to the person I cc-d).
Please send patches via email, not as github pull requests. Again, if you
think it's a security issue, send it directly to my gmail address, but
otherwise please send it to the mailing list, so others can see it and comment
on it.
The preferred format is the files created by git-format-patch, as attachments.
However, if your repo has a public clone URL, you can make a new branch just
for this fix, and send the repo URL and branch name to the mailing list.
(If you do send me a github pull request, I may take it if it's a trivial
patch, but otherwise I'll ask you to close the pull request, then read
this URL for how to send me the patch.)