all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Alexis <flexibeast@gmail.com>
Cc: Katsumi Yamaoka <yamaoka@jpl.org>, emacs-devel@gnu.org
Subject: RE: put input focus on active minibuffer
Date: Sun, 14 Feb 2016 19:01:21 -0800 (PST)	[thread overview]
Message-ID: <636a172f-7790-4245-9c6e-1d7b77d8aa35@default> (raw)
In-Reply-To: <8737suu20f.fsf@gmail.com>

> >> 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.

I see.  You were saying how to do it on one's own, and not
speaking to the OP's feature request for Emacs.  Sorry for
not understanding that.



  reply	other threads:[~2016-02-15  3:01 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
2016-02-15  3:01         ` Drew Adams [this message]
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

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

  git send-email \
    --in-reply-to=636a172f-7790-4245-9c6e-1d7b77d8aa35@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=flexibeast@gmail.com \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.