From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#26513: 25.2; pop-up-frames and *Completions* buffer Date: Sun, 16 Apr 2017 09:16:31 +0200 Message-ID: <58F31A4F.9010002@gmx.at> References: <58F23339.6090201@gmx.at> <58F27723.8010706@gmx.at> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1492327039 17666 195.159.176.226 (16 Apr 2017 07:17:19 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 16 Apr 2017 07:17:19 +0000 (UTC) Cc: 26513@debbugs.gnu.org To: "Charles A. Roelli" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Apr 16 09:17:15 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1czeQs-0004KN-9V for geb-bug-gnu-emacs@m.gmane.org; Sun, 16 Apr 2017 09:17:14 +0200 Original-Received: from localhost ([::1]:59505 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1czeQt-0000zE-9F for geb-bug-gnu-emacs@m.gmane.org; Sun, 16 Apr 2017 03:17:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35868) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1czeQj-0000z4-PB for bug-gnu-emacs@gnu.org; Sun, 16 Apr 2017 03:17:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1czeQh-0008Kg-3h for bug-gnu-emacs@gnu.org; Sun, 16 Apr 2017 03:17:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:51500) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1czeQh-0008KT-0A for bug-gnu-emacs@gnu.org; Sun, 16 Apr 2017 03:17:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1czeQg-0007aY-RX for bug-gnu-emacs@gnu.org; Sun, 16 Apr 2017 03:17:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 16 Apr 2017 07:17:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 26513 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 26513-submit@debbugs.gnu.org id=B26513.149232701029130 (code B ref 26513); Sun, 16 Apr 2017 07:17:02 +0000 Original-Received: (at 26513) by debbugs.gnu.org; 16 Apr 2017 07:16:50 +0000 Original-Received: from localhost ([127.0.0.1]:49695 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1czeQU-0007Zm-Iu for submit@debbugs.gnu.org; Sun, 16 Apr 2017 03:16:50 -0400 Original-Received: from mout.gmx.net ([212.227.17.20]:50699) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1czeQS-0007ZY-67 for 26513@debbugs.gnu.org; Sun, 16 Apr 2017 03:16:48 -0400 Original-Received: from [192.168.1.100] ([213.162.68.14]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lr46Z-1cLLel3oep-00eYqG; Sun, 16 Apr 2017 09:16:41 +0200 In-Reply-To: X-Provags-ID: V03:K0:+Q4A70c0ph7MyWqWJqfmvdbbW/Tcs159oyv3qBkh+GX6tXtNH/0 78wTseRRlFhJt1hrS6nCOLfDmhTDyZa6ZAcHh8bCpZX48H0zAYlunaCAXOPxsSfHOF6Am+P bgPfbkdEuH2Nr1w6xN9xDExR63fhM4Iiw2sVNSm0luB5TcX3YnnYG32x5tRrHs45dBWIzml qefA4itpjTsFG6skfsNeg== X-UI-Out-Filterresults: notjunk:1;V01:K0:rbrrEOerLOw=:UtUluDGgHqbgLZGp6vvmA0 JigISElloIFm1kMapl1/4R7x2/JklEliYAJCndmuGUy3RjUK0E7EBptMW7jCfv4FtB20AWFtl T2FFgXGj2psinE3fjwKpzViuacgw8IsYHSnY4vhk5j2xklTqWbbuZDX7WZdh20x7VT+x6+Nhw AscmBgMmSV4FkgXo4jq0++UMgQIg6vHbMTK7wIyn0hMOlMdfK5rtGWuavC58Sb9t2dapy+tPJ RP+EWXydlegImTDF7mqhd/MYhpdqJkNTgPc24I5AEMU1VHRU96t+EpGgM0A+93cItEwIl8YPu jrcjhIUjK7jE+f1AL8FVUlCMoXCQalUGlLQgaw0SCNWPEqCySysikwIZlpV03fBWB1V1YukI6 Khj0vsJmu7Z6xz963756xggPlyAUvANJEO/+sk6ie6L2paq5qooI1skBfvfY8pQ8efEu6Pxuo DTOKhqORN0OF4yL67XDowaRIFdNn1j//pX1etK+2zu7n5ZaKcv2zbY2qSNZOLtYxOOyyel1pC vfYkOndNiMWE5hUs0WokXHtuD1IGt1sMlKMAyw8MGomJBGWS6+sT1WoGT2Lqfv9Yap1eABD3m TjvNjkL/GnwSznKlvqNnfPT0m+cXLJhxJMs1f2Iw+arE1KPZqJe0RjLZEmaglOYPTDvVu30Yg CXDEcf8VsW0wF2cfazi3z9pUwqqBFrBYacg4xUIIyTv2arTqei/NE7GxX+mpmgdopBJbm8rqA gQxgdFEr41DjgWUEt1E+jtxBiV0QhJ5kOm3CcuUAsHd0D38N4ve/tJBSx8+eARF2MR9ocJBr X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:131644 Archived-At: > Really? But selecting a completion with the mouse or with RET in the > *Completions* window with pop-up-frames set to nil does the same. Yes. But I never noticed. I could have sworn that I had to type RET somewhere to confirm that I really wanted to do what I picked with the mouse or via RET in the *Completions* buffer before. > Granted, though, it's probably not a very common thing to do. > > And also, sorry if this was not clear, but this bug is for completion > everywhere in Emacs, not just M-x. That's why I asked. I now think that for most users the behavior that the frame is selected is quite normal (for M-x) and I rather would expect the *Completions* window to be selected too when it appears on the same frame. The current behavior is inconsistent. > Thank you; I wasn't aware of this. Now it makes sense why the > *Completions* frame gets focus. One solution to this problem, then, > might be to create a separate *Completions* frame on startup and update > it with completions as necessary, without ever deleting/recreating it. > I'll see if I can write a mode or something for this. Even then it might get focus. With a focus follows mouse policy, raising a frame that happens to be under the mouse pointer will usually also focus it (blame the window manager for that). >> Still, why would you want to "continue typing in the minibuffer" when >> the desired effect of what you do is to choose and execute one of the >> commands shown in the *Completions* buffer? > > As explained above, it isn't necessarily the desired effect, only one > example. Maybe it would then make sense to discriminate the use cases of *Completions*: One where continuing typing in the selected window wouldn't make sense because one has to select an item in the *Completions* buffer. In that case selecting the *Completions* window makes perfect sense IMHO. And one where you usually want to continue typing and the *Completions* buffer is just there for later perusal. martin