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:02:26 +0300 [thread overview]
Message-ID: <838sggv23x.fsf@gnu.org> (raw)
In-Reply-To: <a94fb637-bc94-f185-590a-76bc9ff76741@gmail.com> (Herman@debbugs.gnu.org)
> From: Herman@debbugs.gnu.org, Géza <geza.herman@gmail.com>
> Date: Sun, 21 Jun 2020 17:43:09 +0200
>
> I noticed that the call "(select-window win)" in term.el (in
> term-emulate-terminal) interacts badly with doom modeline. This
> select-window call confuses the modeline which is the active window, and
> it causes the terminal's modeline displayed as active, as soon as the
> terminal receives output, no matter which is the actual active window.
> And the real active window is displayed with an inactive modeline.
>
> I found if I modify this "(select-window win)" line to "(select-window
> win t)", the bug doesn't happen anymore (I'm not sure whether it's a
> correct fix in all regards or not).
>
> Here's my full description of the issue, with screenshot:
> https://github.com/seagle0128/doom-modeline/issues/355
>
> Describe: When one window has an ansi-term, which constantly outputs
> some text, and another window has the focus, then doom-modeline behaves
> strange: the mode line of the focused window loses activity, and part of
> ansi-term's mode line becomes active.
Any reason why you decided this isn't a doom modeline bug?
next prev parent reply other threads:[~2020-06-21 16:02 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 [this message]
2020-06-21 16:18 ` Herman, Géza
2020-06-21 16:30 ` Eli Zaretskii
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=838sggv23x.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).