Omar Antolín Camarena

Right, I think the hooks are a little more complicated. Even a hypothetical post-act-all hook as you say would need to know whether the selection was acted on or not:...

I agree with @minad that you can give yourself an even better keybinding by defining your own variant of embark-dwim. But maybe it's worth adding a `:default-action` key to `embark-quit-after-action`°

> On the other hand the option you suggested might be a bit too much of a special case. Note also that I would want the opposite, :`except-for-default-action`. I'm not...

But probably @minad's suggestion is even better for you since you get a shorter keybinding than `C-. RET`.

I'll check when I'm at the computer, but I'm pretty sure I know what's going on. What embark-act-all does is just run the action in a loop, passing to it...

One way to deal with this is to temporarily set `uniquify-after-kill-buffer-p` to `nil` when using `kill-buffer` as an action: ```elisp (cl-defun no-uniquify-after-kill-buffer (&rest args &key run &allow-other-keys) (let (uniquify-after-kill-buffer-p) (apply...

You can write your own multi-target actions that receives a list of buffer names, looks up the actual buffers and kills them: ```elisp (defun kill-each-buffer (buffer-names) "Kill each buffer whose...

The second solution is better, you probably only need to try that one. About closing: let's keep it open for a bit while I think about whether to make a...

I could go either way on this one. I don't share @minad's worry about target finders that match anywhere in a buffer, because of my experience with the buffer target...

> maybe Embark already comes last anyway since it already matches too often. ;) 😄