all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>, emacs-devel <emacs-devel@gnu.org>
Subject: RE: eldoc vs minibuffer-auto-raise
Date: Sat, 19 Jan 2019 08:20:59 -0800 (PST)	[thread overview]
Message-ID: <fdf8f1a8-b7df-4a55-a818-f93ccebf139c@default> (raw)
In-Reply-To: <5C42EEA3.70808@gmx.at>

> (setq minibuffer-auto-raise t)
> and then in *scratch* I start typing something like
> (setq
> A short pause here switches focus to the minibuffer frame and typing
> the subsequent space character gets me
> 
> SPC is undefined
> 
> Obviously, eldoc intervenes here since doing the same with Emacs 24
> proceeds without problems.
> 
> I'd like to know whether people using separate minibuffer frames see
> this problem, circumvent it by not using 'minibuffer-auto-raise' or
> disabling 'eldoc-mode' or whatever exists to handle this behavior in a
> reasonable way.  If there was a previous discussion about this, please
> point me to it.

I mention this because you asked about uses of standalone
minibuffer frames.  But I'm pretty sure it won't help you.
I didn't try from `emacs -Q', and my setup is far from
`emacs -Q'.

I use a standalone minibuffer frame.  I have eldoc turned
on and `minibuffer-auto-raise' = t.

I don't see (e.g. with Emacs 26) what you describe.  In my
case focus does not switch to the minibuffer frame.

I'm using MS Windows.  Perhaps the window mgr is involved
here, switching the focus to the minibuffer frame in your
case?



  reply	other threads:[~2019-01-19 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19  9:32 eldoc vs minibuffer-auto-raise martin rudalics
2019-01-19 16:20 ` Drew Adams [this message]
2019-01-19 18:49   ` martin rudalics
2019-01-19 19:24     ` Eli Zaretskii
2019-01-20  9:13       ` martin rudalics
2019-01-19 22:25     ` Drew Adams
2019-01-20  9:18       ` martin rudalics

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=fdf8f1a8-b7df-4a55-a818-f93ccebf139c@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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.