unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexis <flexibeast@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Katsumi Yamaoka <yamaoka@jpl.org>, emacs-devel@gnu.org
Subject: Re: put input focus on active minibuffer
Date: Mon, 15 Feb 2016 13:43:28 +1100	[thread overview]
Message-ID: <8737suu20f.fsf@gmail.com> (raw)
In-Reply-To: <daa03d0e-d292-435b-a4b4-a748ea0f868a@default>


Drew Adams <drew.adams@oracle.com> writes:

>> > No, please do not do this.  A user should be able to select 
>> > different buffers and windows, including by clicking the 
>> > mouse or using keyboard keys, while the minibuffer is active. 
>> > A user should be able to do all kinds of things while the 
>> > minibuffer is active - including come back to the minibuffer 
>> > to continue inputting text there etc.
>> 
>> Agreed.
>> 
>> But, if using GNU Emacs 24.4 or later, perhaps make use of 
>> `focus-in-hook`? For example, something along the lines of:
>> 
>>     (defun focus-to-active-minibuffer () 
>>       (if (minibuffer-window-active-p (minibuffer-window)) 
>>           (select-window (minibuffer-window))))
>> 
>>     (add-hook 'focus-in-hook #'focus-to-active-minibuffer)
>
> If you do that then whenever a frame receives the focus so will 
> its (active) minibuffer window.  That precludes the user 
> interactions I described above, and about which you "Agreed".

Well, my suggestion was code to help the OP achieve the effect 
they want, without any other GNU Emacs users being affected. i'm 
sorry that my wording seems to have conveyed the impression that i 
was suggesting that my code be incorporated directly into GNU 
Emacs itself.


Alexis.



  reply	other threads:[~2016-02-15  2:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 10:19 put input focus on active minibuffer Katsumi Yamaoka
2016-02-12 14:53 ` Drew Adams
2016-02-14  4:52   ` Alexis
2016-02-14 16:54     ` Drew Adams
2016-02-15  2:43       ` Alexis [this message]
2016-02-15  3:01         ` Drew Adams
2016-02-15  4:34       ` Yuri Khan
2016-02-20  2:26 ` John Wiegley
2016-02-22 23:43   ` Katsumi Yamaoka
2016-02-24  2:22   ` Elias Mårtenson
  -- strict thread matches above, loose matches on Subject: below --
2016-02-15  6:37 Alexis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737suu20f.fsf@gmail.com \
    --to=flexibeast@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=yamaoka@jpl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).