unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vangelis Evangelou <evangelou@gmail.com>
Cc: 70046@debbugs.gnu.org
Subject: bug#70046: 29.3; ebuffers mini frame loses focus
Date: Thu, 28 Mar 2024 11:22:21 +0200	[thread overview]
Message-ID: <86jzlmhfsi.fsf@gnu.org> (raw)
In-Reply-To: <CAD1AF2c+d+WN6SHPfatC++xkQ0mHxwKUy8uFy3O8BKVDLddo2Q@mail.gmail.com> (message from Vangelis Evangelou on Thu, 28 Mar 2024 08:36:56 +0000)

> From: Vangelis Evangelou <evangelou@gmail.com>
> Date: Thu, 28 Mar 2024 08:36:56 +0000
> 
> When using ebuffers with the default settings, going up and down on differences by pressing n and p switches
> focus to the buffers that are being compared. As an example, run the following commands in terminal:
> 
> ping -c 10 example.com > ~/fileA
> ping -c 10 example.com > ~/fileB
> emacs -Q --eval '(ebuffers (find-file "~/fileA") (find-file "~/fileB"))'
> 
> and then press n and p to navigate through the differences. You will notice that focus switches to the buffers.
> It doesn't happen always.

I cannot reproduce this.  I tried many times.

How do you see that focus switches to one of the buffers being
compared?





  reply	other threads:[~2024-03-28  9:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  8:36 bug#70046: 29.3; ebuffers mini frame loses focus Vangelis Evangelou
2024-03-28  9:22 ` Eli Zaretskii [this message]
2024-03-28 10:08   ` Vangelis Evangelou
2024-03-28 10:28     ` Eli Zaretskii
2024-03-28 10:35       ` Vangelis Evangelou
2024-03-28 10:39         ` Vangelis Evangelou
2024-03-28 11:30         ` Eli Zaretskii
2024-03-28 12:59         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-28 14:27           ` Vangelis Evangelou
2024-04-05  7:55             ` Vangelis Evangelou
2024-04-05  8:13               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-05  8:31                 ` Vangelis Evangelou
2024-04-07  3:43                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=86jzlmhfsi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70046@debbugs.gnu.org \
    --cc=evangelou@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).