all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: martin rudalics <rudalics@gmx.at>
Cc: 36680@debbugs.gnu.org
Subject: bug#36680: 27.0.50; undo-tree visualizer flickering with display-buffer-reuse-frames -> t
Date: Thu, 18 Jul 2019 04:38:24 +0200	[thread overview]
Message-ID: <871ryo12zj.fsf@web.de> (raw)
In-Reply-To: <73a9bb70-d34f-9229-ca4b-12701c3082f8@gmx.at> (martin rudalics's message of "Wed, 17 Jul 2019 10:39:37 +0200")

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

martin rudalics <rudalics@gmx.at> writes:

> I don't know why 'undo-tree' apparently insists on switching to its
> buffer here but if you put it on another frame you have to live with
> the fact that that frame will be raised.

I think you didn't understand what I tried to describe.  I attach a
video demonstration (hope that works).

I don't put the visualizer to another frame, that's not the case and not
the problem.

It's the visualizer that looks if the buffer is displayed not only in
the current frame, but also in another frame, and raises this other
frame when there is one.

> I think you should make a special rule for 'display-buffer' to not
> display the undo tree on a separate frame.

As said, this is not the problem.

> Note also that 'display-buffer-reuse-frames' is an obsolete variable.

I think also other settings could lead to this effect.


Thanks,

Michael.


[-- Attachment #2: Emacs Bug#36680.webm --]
[-- Type: video/webm, Size: 225340 bytes --]

  reply	other threads:[~2019-07-18  2:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 22:23 bug#36680: 27.0.50; undo-tree visualizer flickering with display-buffer-reuse-frames -> t Michael Heerdegen
2019-07-17  8:39 ` martin rudalics
2019-07-18  2:38   ` Michael Heerdegen [this message]
2019-07-18  3:01     ` Michael Heerdegen
2019-07-18  7:49       ` martin rudalics
2019-07-18 21:13         ` Michael Heerdegen
2019-07-19  8:16           ` martin rudalics
2019-07-19 21:49             ` Michael Heerdegen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871ryo12zj.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=36680@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.