Remove unnecessary util load guard #132
Open
+0
−7
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.
Fix Mundo_PluginLoaded is stored in sessions.
Autoload files don't need a load guard because vim only sources them when calling an autoload function that doesn't exist. Once util.vim is sourced, all of its functions are defined and it doesn't need to get called again.
If we kept the load guard, it should be called something like g:mundo_loaded_util so users with global in 'sessionoptions' (not the default) won't have the variable stored in their session. I think that would cause problems if you used a plugin manager to defer load mundo, loaded a session, and then loaded mundo. (plugin/mundo.vim calls mundo#util functions so util.vim is sourced on startup. Otherwise, this would be a more widespread problem.)
Test