From: Eli Zaretskii <eliz@gnu.org>
To: Herman@debbugs.gnu.org, Géza <geza.herman@gmail.com>
Cc: 41984@debbugs.gnu.org
Subject: bug#41984: 28.0.50; term.el's select-window call interacts badly with modeline
Date: Sun, 21 Jun 2020 19:30:22 +0300 [thread overview]
Message-ID: <835zbkv0td.fsf@gnu.org> (raw)
In-Reply-To: <3e5250a8-2e92-f8e7-0de1-68d61463981e@gmail.com> (message from Herman, Géza on Sun, 21 Jun 2020 18:18:20 +0200)
> Cc: 41984@debbugs.gnu.org
> From: Herman, Géza <geza.herman@gmail.com>
> Date: Sun, 21 Jun 2020 18:18:20 +0200
>
> I don't have a strong opinion on this. I just felt that selecting a
> window because an output arrived is not a right thing to do.
I don't see why this would not be a right thing to do. Presumably,
term.el wants to attract the user's attention to the fact that new
input arrived.
> Any hooks
> which are called during this temporarily set selected-window will have
> the wrong idea which is the actual selected window (I'm not exactly
> sure, why the bug happens though, I just suppose this is the reason).
>
> I've checked now, spaceline behaves exactly the same as doom modeline.
> But if you think that this is not a term.el bug, please tell the
> reasons, and I'll reopen my doom-modeline issue with these reasons.
I think the hooks that do something with the modeline need to be able
to handle this situation, or, failing that, disable themselves when
the selected window displays a term.el buffer.
next prev parent reply other threads:[~2020-06-21 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 15:43 bug#41984: 28.0.50; term.el's select-window call interacts badly with modeline Herman, Géza
2020-06-21 16:02 ` Eli Zaretskii
2020-06-21 16:18 ` Herman, Géza
2020-06-21 16:30 ` Eli Zaretskii [this message]
2020-06-21 18:18 ` Herman, Géza
2020-06-21 19:03 ` Herman, Géza
2021-09-17 16:38 ` Lars Ingebrigtsen
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=835zbkv0td.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=41984@debbugs.gnu.org \
--cc=Herman@debbugs.gnu.org \
--cc=geza.herman@gmail.com \
/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).