Initialization works the same way as with regular plugins - with regular plugins I will have some code in my ./plugin folder (not my ./pack/start/* folder(s)... this ./plugin code will run unequivocally on startup. However, if I only wanted to run that code when I packadd matchit or something like that... then how do I do THAT. What is the mechanism of step 3? A plugin will have it's own ``./pack/opt/bundle/some_plugin/plugin/init.lua` folder to initialize itself. But I want to do additional work in my ./plugin/additional_config_for_some_plugin.lua file

Another thing I will do is load hs objects when I open a file up in ~/.hammerspoon. I love that I can easily code up this power in my ftplugin file, but DANG I'm struggling

I want to run one-time setup when my optional plugin (to be loaded with packadd) is loaded. But I cannot find the Autocmd to run after a packadd. Maybe there is an autocmd after a require was my next thought.

@Rich You're right, the command should have been --listen. I will edit my answer

@D.BenKnoble when you’re right, you’re right 😂… literally in the title… hard to pull myself out of the context of achieving the solution (the vimdiff window) and back to the ask! When the question said patch I didn’t think it implied a git diff. It no longer says patch tho.

@D.BenKnoble good point. Although I likely suspect OP doesn’t even want to use git diff without a specific filepath for diff creation in the first place…