aboutsummaryrefslogtreecommitdiff
path: root/runtime/syntax/python.vim
diff options
context:
space:
mode:
authorBirdee <85372418+BirdeeHub@users.noreply.github.com>2025-08-21 10:08:29 -0700
committerGitHub <noreply@github.com>2025-08-21 10:08:29 -0700
commitc522cb0e96dad3bf3a834df5c6a8988f5c13a1a3 (patch)
tree03a2b80267a432a335eb0aaa0243dff15b48f32c /runtime/syntax/python.vim
parent94677318655eb803fccef4409834b6b77e11282a (diff)
downloadrneovim-c522cb0e96dad3bf3a834df5c6a8988f5c13a1a3.tar.gz
rneovim-c522cb0e96dad3bf3a834df5c6a8988f5c13a1a3.tar.bz2
rneovim-c522cb0e96dad3bf3a834df5c6a8988f5c13a1a3.zip
feat(pack): support user-defined `data` in plugin spec #35360
Problem: The load function in opts was difficult to use if you wished to customize based on the plugin being loaded. You could get the name, but without some way to mark a spec, that was of limited usefulness unless you wanted to hardcode a list of names in the function, or write a wrapper around the whole thing Solution: Allow users to provide an arbitrary data field in plugin specs so that they may receive info as to how to handle that plugin in load, get() and events, and act upon it Co-authored-by: BirdeeHub <birdee@localhost> Co-authored-by: Evgeni Chasnovski <evgeni.chasnovski@gmail.com>
Diffstat (limited to 'runtime/syntax/python.vim')
0 files changed, 0 insertions, 0 deletions