Omar Antolín Camarena

I've actually made use of the fact that the selection remains after `delete-region`: after `delete-region` you can still `embark-insert` the deleted text to bring it together, for example. But I...

Yeah, I've been thinking that maybe I should add an indicator (this is a technical term: the functions that go in `embark-indicators`) saying how many items are selected.

I'm not sure taking up space in the modeline is warranted. Don't you only need to know whether there is a selection or not when you call `embark-act`? That's why...

OK, that sounds reasonable, but I think the mode line indicator should be wrapped up in a minor mode, no? Automatically messing with people's mode lines is a sure-fire way...

And further thinking about this issue, I think maybe a new user option `embark-deselect-after-action` is reasonable. It would be like `embark-quit-after-action`: either a boolean or an alist for fine-grained control....

Which actions do you use that as a post-action hook for, @localauthor?

@minad With the current information that hooks get, a hook can't know whether you acted on the selection or not. So currently, the best you could do with hooks is...

> Hmm, thinking about this more I wonder if maybe a post action hook is not the correct abstraction. Acting on a selection is triggered by embark-act-all while post action...

It's not a problem that the hook gets called repeatedly. What would happen precisely is that, if the action is on `embark-multitarget-actions`, then the hook gets called once with `:candidates`...

Another issue is whether we'd want collect and export to also clear the selection. I think we probably would. But those commands can be called directly, without going through `embark-act-all`...