|
From: | martin rudalics |
Subject: | bug#28978: 26.0; Regression: separate, dedicated `*Completions*' frame no longer has parameter `minibuffer' |
Date: | Sat, 28 Oct 2017 10:45:27 +0200 |
> So the meaning of frame-parameter `minibuffer' has changed. Not really. It should specify the minibuffer window used by that frame if the frame doesn't have its own minibuffer window. Otherwise, it's t if this is a normal frame with its own minibuffer window and 'only if it's a minibuffer-only frame. nil only serves as an initial value where it's up to Emacs to decide which minibuffer window to choose (something it eventually may have to do anyway). > I will need to adjust my code somehow. > > How would you suggest I change the test I have been using, > to detect a frame that has the active minibuffer (versus > the case I reported, where dedicated frame `*Completions*' > has no minibuffer)? I would try (eq (minibuffer-selected-window) (frame-selected-window this-frame)) It's a pity that you were not around when I tried to discuss the associated code here. Maybe together we would have found a more convenient solution. martin
[Prev in Thread] | Current Thread | [Next in Thread] |