From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>, Phil Sainty <psainty@orcon.net.nz>
Cc: larsi@gnus.org, mkupfer@alum.berkeley.edu, 50743@debbugs.gnu.org,
jidanni@jidanni.org
Subject: bug#50743: Emacsclient not tested vs. Local Variables prompt
Date: Sun, 26 Sep 2021 11:12:05 +0200 [thread overview]
Message-ID: <6d2a81e7-778f-719f-9a35-04a8ef388366@gmx.at> (raw)
In-Reply-To: <83zgrzontw.fsf@gnu.org>
> And if you set server-raise-frame to nil, the "problem" happens in
> both cases, right?
>
> So I'm not sure this is a bug. The user should switch to the correct
> frame to answer the question. On my system, there's a prominent
> indication that the client frame needs my attention, but even if there
> isn't, the user should be vigilant enough to type the response into
> the right frame.
>
> If we do want to somehow raise the frame earlier, we should do it
> conditioned by server-raise-frame, because some users don't want the
> frame to raise and get input focus. But it isn't clear to me where
> would be the correct place to raise the frame "earlier".
Maybe 'server-raise-frame' does too much when it triggers
'select-frame-set-input-focus'. Still I consider it a bug when the user
gets prompted and the frame displaying the prompt doesn't have focus.
martin
next prev parent reply other threads:[~2021-09-26 9:12 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 20:16 bug#50743: Emacsclient not tested vs. Local Variables prompt 積丹尼 Dan Jacobson
2021-09-22 20:40 ` Lars Ingebrigtsen
2021-09-23 5:43 ` 積丹尼 Dan Jacobson
2021-09-23 6:54 ` Phil Sainty
2021-09-24 8:23 ` 積丹尼 Dan Jacobson
2021-09-24 14:11 ` Phil Sainty
2021-09-24 14:42 ` 積丹尼 Dan Jacobson
2021-09-25 1:12 ` Phil Sainty
2021-09-25 4:18 ` 積丹尼 Dan Jacobson
2021-09-25 5:07 ` Phil Sainty
2021-09-25 5:46 ` 積丹尼 Dan Jacobson
2021-09-25 8:33 ` Phil Sainty
2021-09-25 13:06 ` 積丹尼 Dan Jacobson
2021-09-25 14:02 ` Phil Sainty
2021-09-25 22:55 ` Mike Kupfer
2021-09-26 0:19 ` Mike Kupfer
2021-09-26 2:57 ` Mike Kupfer
2021-09-26 0:34 ` Phil Sainty
2021-09-26 2:48 ` Mike Kupfer
2021-09-26 6:25 ` Eli Zaretskii
2021-09-26 9:12 ` martin rudalics [this message]
2021-09-26 9:19 ` Eli Zaretskii
2021-09-26 9:59 ` martin rudalics
2021-09-26 11:03 ` Eli Zaretskii
2021-09-26 17:50 ` martin rudalics
2021-09-26 18:19 ` Eli Zaretskii
2021-09-27 8:50 ` martin rudalics
2021-09-27 14:32 ` Jean Louis
2021-09-27 17:15 ` martin rudalics
2021-09-26 17:51 ` Mike Kupfer
2021-09-26 18:26 ` Eli Zaretskii
2021-09-26 22:08 ` Mike Kupfer
2021-09-27 4:48 ` Eli Zaretskii
2021-09-27 8:50 ` martin rudalics
2021-09-27 14:35 ` Jean Louis
2021-09-26 17:02 ` Mike Kupfer
2021-09-26 6:53 ` 積丹尼 Dan Jacobson
2021-09-26 7:12 ` Eli Zaretskii
2021-09-26 7:20 ` 積丹尼 Dan Jacobson
2021-09-26 7:31 ` 積丹尼 Dan Jacobson
2021-09-26 7:41 ` 積丹尼 Dan Jacobson
2021-09-26 20:49 ` 積丹尼 Dan Jacobson
2021-09-27 4:43 ` Eli Zaretskii
2021-09-27 17:30 ` 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
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=6d2a81e7-778f-719f-9a35-04a8ef388366@gmx.at \
--to=rudalics@gmx.at \
--cc=50743@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.org \
--cc=mkupfer@alum.berkeley.edu \
--cc=psainty@orcon.net.nz \
/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).