At #88, @uga-rosa proposed to me a new variable, g:jetpack_skip_config, to skip executing the config setting because the config containing require(...) usually fails in the test on CI.
This reason is the same as #91. At #88, @uga-rosa says that the variable is only for developers and not for users. However, according to #91, we need to employ this approach even for users.
The variable approach is not good for preventing the execution of config at the initial (setup) phase because we need to manually update the variable from 0 to 1 after installing all plugins. Here, we propose the following changes. Would you mind reviewing this change, @uga-rosa and @gw31415?
jetpack#merge produces a log file packages.json of what plugins are deployed (merged).
jetpack#tap checks the availability based on the log file.
use syntax defines the local function setup_{inner,outer} and config_{inner,outer} with jetpack#tap
the config function is kicked after the event JetpackEnd. The previous version kicks the functions with the map function but this version kicks the function by the event. I claim that this is the vim-way.
tani
commented
2 years ago
At #88, @uga-rosa proposed to me a new variable,
g:jetpack_skip_config, to skip executing theconfigsetting because the config containingrequire(...)usually fails in the test on CI. This reason is the same as #91. At #88, @uga-rosa says that the variable is only for developers and not for users. However, according to #91, we need to employ this approach even for users. The variable approach is not good for preventing the execution of config at the initial (setup) phase because we need to manually update the variable from 0 to 1 after installing all plugins. Here, we propose the following changes. Would you mind reviewing this change, @uga-rosa and @gw31415?packages.jsonof what plugins are deployed (merged).usesyntax defines the local functionsetup_{inner,outer}andconfig_{inner,outer}withjetpack#tapconfigfunction is kicked after the eventJetpackEnd. The previous version kicks the functions with themapfunction but this version kicks the function by the event. I claim that this is the vim-way.