emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Stephen Paul Weber <singpolyma@singpolyma.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: display-buffer-pop-up-frame causes many extra frames for capture
Date: Sun, 06 Sep 2020 08:31:35 +0200	[thread overview]
Message-ID: <87tuwbl8l4.fsf@gnu.org> (raw)
In-Reply-To: <20200503033854.GA28741@singpolyma-beefy> (Stephen Paul Weber's message of "Sat, 2 May 2020 22:38:54 -0500")

Hi Stephen,

Stephen Paul Weber <singpolyma@singpolyma.net> writes:

> I'm happy to make further customisations of my environment to avoid
> this, but it is very surprising to me so I wonder if anyone can
> guess what might be happening and give me some pointers about it?

I don't use frames so I cannot confirm the bug is *not* here, perhaps
others can tell.

In the meantime, can you provide your Org and Emacs versions and a
reproducible minimal recipe for what looks like a bug?  A few steps
to let anyone see what you see and fix the problem.



      reply	other threads:[~2020-09-06  6:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-03  3:38 Stephen Paul Weber
2020-09-06  6:31 ` Bastien [this message]

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=87tuwbl8l4.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=singpolyma@singpolyma.net \
    --subject='Re: display-buffer-pop-up-frame causes many extra frames for capture' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).