Two users, @shadowwa and @dmaes reported errors where vim 9.1 was not happy about the variable g:puppet_display_errors not being defined when evaluating syntax/puppet.vim. They found out that the order the plugin scripts were loaded did not reflect my current understanding of how vim loads plugin files: the syntax file was loaded before the ftplugin script, so the variable was indeed not yet defined.
Since the variable is only used in the syntax script, we can declare its default value there if the variable doesn't exist (instead of in the ftplugin file)
I've also changed to using the more common values 0/1 for binary flags in order to use vimscript's "truthy/falsy" nature of a variable.
Two users, @shadowwa and @dmaes reported errors where vim 9.1 was not happy about the variable g:puppet_display_errors not being defined when evaluating
syntax/puppet.vim
. They found out that the order the plugin scripts were loaded did not reflect my current understanding of how vim loads plugin files: the syntax file was loaded before the ftplugin script, so the variable was indeed not yet defined.Since the variable is only used in the syntax script, we can declare its default value there if the variable doesn't exist (instead of in the ftplugin file)
I've also changed to using the more common values 0/1 for binary flags in order to use vimscript's "truthy/falsy" nature of a variable.
(Closes: #151)