From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Org-Agenda leaves frame around [9.7-pre (release_9.6.8-785-g72bbf8.dirty @ /home/bidar/.local/private/etc/emacs/lib/org/lisp/)]
Date: Sat, 09 Mar 2024 05:21:39 +0200 [thread overview]
Message-ID: <874jdg2ipo.fsf@> (raw)
In-Reply-To: <87msrmb6u6.fsf@localhost> (Ihor Radchenko's message of "Tue, 27 Feb 2024 09:21:37 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> Ihor Radchenko <yantar92@posteo.net> writes:
>
>>> 0. emacs -Q
>>> 1. Paste this into the scratch buffer:
>>> (setq org-agenda-window-setup 'other-frame)
>>> (setq pop-up-frames t)
>>> 2. Eval
>>> 3. Org-agenda
>>
>> This is now expected.
>> We changed Org agenda to respect user settings, including
>> `pop-up-frames' setting.
>> ...
>
> Oops. I missed that the problem is not with a new frame with agenda
> commands, but with the frame not being closed.
>
> Fixed, on main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=fef873b1c
I noticed that `org-insert-structure-template' and possibly others are
also affected
Is a new bug needed or this one enough?
next prev parent reply other threads:[~2024-03-09 3:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 8:38 [BUG] Org-Agenda leaves frame around [9.7-pre (release_9.6.8-785-g72bbf8.dirty @ /home/bidar/.local/private/etc/emacs/lib/org/lisp/)] Björn Bidar
2024-02-23 13:29 ` Ihor Radchenko
2024-02-23 13:46 ` Björn Bidar
2024-02-23 13:53 ` Ihor Radchenko
2024-02-27 8:52 ` Björn Bidar
2024-02-27 9:07 ` Ihor Radchenko
2024-02-27 9:21 ` Ihor Radchenko
2024-02-27 10:42 ` Björn Bidar
2024-03-09 3:21 ` Björn Bidar [this message]
2024-03-12 12:14 ` Ihor Radchenko
2024-04-05 11:25 ` Björn Bidar
2024-04-10 12:46 ` Ihor Radchenko
2024-04-14 3:33 ` Björn Bidar
2024-04-14 12:57 ` Ihor Radchenko
2024-04-16 5:08 ` Björn Bidar
2024-04-17 17:26 ` Ihor Radchenko
2024-04-29 18:50 ` Björn Bidar
2024-04-29 19:25 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jdg2ipo.fsf@ \
--to=bjorn.bidar@thaodan.de \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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/org-mode.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).