Alternatives for "load bundle" etc functionality?

[Lippiece]

Looks like #448 wipes out --all-- most of the functionality of the plugin I use. I use it to tie the run dev commands and alike to the nvim instance (with bundles), so that when I'm finished, I can just :qa without worrying about dangling processes.

Can someone recommend an alternative?

[stevearc]

Sorry, what part of that PR removes the functionality that you're using? From your description it just sounds like you're running tasks in nvim, which of course still works.

[Lippiece]

I mostly use the bundle functionality. Seems like I was mistaken about PR removing the everything I use, since I also use "run command" (which is replaced).

[Lippiece]

I may be confused about saving tasks still being available, though, but this definitely sounds like bundles.

[stevearc]

The API for serializing tasks still exists, but the convenience methods of working with bundles specifically are removed. How are you using them? In my personal experience whenever I would want to save a task it was actually better to just define it in a template instead.

[Lippiece]

I run commands with OverseerRun, then OverseerSaveBundle, then OverseerLoadBundle. Not sure what templates are.

Ah, I see the templates. When I started to use the plugin, I was looking for exactly what bundles do. Templates require defining them, but bundles can be saved and loaded without updating the config.

[stevearc]

What value are you getting from the save/load bundle instead of just doing OverseerRun again? Are you making modifications to the tasks before saving them? Or are you saving multiple tasks so that you can start them again with a single OverseerLoadBundle?