Daniel Mendler

About the unselect after action - do we need a separate option for that or is a post action hook already sufficient? We already configure them per action and Embark...

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 hooks...

@oantolin > Obviously we could add a user option embark-deselect-after-action, but we could instead pass an extra argument to hooks indicating whether the selection was acted on. If we add...

> A post-action hook could still work if it knew that you had acted on the selection. It would have to handle two cases still: whether you used a multitarget...

Okay, I see. And we would still need the additional keyword argument telling the hook if we are operating in a selection or not, right? When operating on a selection...

> Even a hypothetical post-act-all hook as you say would need to know whether the selection was acted on or not: in Embark's default configuration the selection is the highest...

Why not use `M-.`? You could write your own command which let-binds `embark-quit-after-action`.

@Hugo-Heagren Let me say first that I am sorry that every time you make a suggestion, I appear with some critical remarks. The problem is that I have a (too?)...

> This is a good place to explain why I wrote this in the first place. I bind quite a few extra keys in help-mode-menu (e.g. a command bound to...

@oantolin > I still have it in my personal configuration, and while I don't use it much I've never felt it go in the way. That's not exactly an argument...