From: Vangelis Evangelou <evangelou@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70046@debbugs.gnu.org
Subject: bug#70046: 29.3; ebuffers mini frame loses focus
Date: Thu, 28 Mar 2024 10:08:51 +0000 [thread overview]
Message-ID: <CAD1AF2eAS+FBhsMqKj-8TNfukaZdAn43ZdU8MPs3jT_Wu0ncQg@mail.gmail.com> (raw)
In-Reply-To: <86jzlmhfsi.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
Because the cursor moves to that buffer and if I press n or p it inserts in
that buffer. Here is a video demonstrating this
https://drive.google.com/file/d/1E7ycJJTYuo62MwViGfiYz_tnornMdXkN/view?usp=sharing
Also, note in the video that the mini frame goes under the top bar. I don't
know if that's an emacs issue though.
On Thu, 28 Mar 2024 at 09:22, Eli Zaretskii <eliz@gnu.org> wrote:
> > 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?
>
[-- Attachment #2: Type: text/html, Size: 1891 bytes --]
next prev parent reply other threads:[~2024-03-28 10:08 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
2024-03-28 10:08 ` Vangelis Evangelou [this message]
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=CAD1AF2eAS+FBhsMqKj-8TNfukaZdAn43ZdU8MPs3jT_Wu0ncQg@mail.gmail.com \
--to=evangelou@gmail.com \
--cc=70046@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).