Setting Vundle key mappings to be silent #659
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
|
@nfischer thanks, i'll take a look ASAP. |
gmarik
added a commit
that referenced
this pull request
Nov 5, 2015
Setting Vundle key mappings to be silent
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.
I set already existing Vundle key mappings to have the
<silent>attribute so that the commands are not echoed onto the command line. This silences commands such as:silent bd!and:exec 'Install'.getline('.')(which can be confusing for users to see echoed to the screen).This should not change actual functionality or performance (so it should be a fairly safe merge), but it should improve user experience.