Simply checking the buffer-list is not enough, because an interactive command can be invoked via various ways, not just directly or via M-x. E.g. if you invoke it via a Helm-like selector package which creates various buffers for selection then the buffer list is affected.
Is there a reliable way to determine the origin buffer of a command which uses the minibuffer for input?
No, there's no way to know what buffer that is, in general.
If you use Icicles then you can know: it's the value of variable icicle-pre-minibuffer-buffer:
Buffer that was current before the minibuffer became active.
icicle-mode minor mode then you can know what that buffer is.)
other-window), I suppose it should come back to the origin buffer. So, I guess that something somewhere should know how to reach this buffer... Maybe it's too hidden in the calling stack or in C code?
current-bufferprovide it?ivy) calling the following command:(defun test (dir) (interactive "D") (print (current-buffer))), it printed the buffer from where I invokedivy-switch-buffer, instead of the minibuffer. I remember something thathelmdoes not use the minibuffer, which could be relevent (or not)... (I can not get the code block formatted 'correctly' here in the comments)minibuffer-setup-hookwhich is called when the cursor is in the minibuffer.