> A quick&dirty workaround for now would be for `completing-read` to set > some var alongside `minibuffer-completion-table` which indicates *which* > minibuffer this is for (e.g. some minibuffer-depth information). > This way `read-from-minibuffer` could distinguish > a `minibuffer-completion-table` passed for the current invocation from > one passed for the outer invocation and could hence temporarily rebind > `minibuffer-completion-table` to nil. This patch is how I thought your suggestion could be implemented, but then later you posted a different patch. Anyway FWIW here is a safer workable workaround that implements your first suggestion and sets a new explicit buffer-local variable in completing minibuffers, so modes that need to distinguish such minibuffers could check it. Maybe this minibuffer-with-setup-hook could be moved even to 'completing-read'?