From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>, Eli Zaretskii <eliz@gnu.org>
Cc: 10873@debbugs.gnu.org, larsi@gnus.org
Subject: bug#10873: 24.0.93; `report-emacs-bug' obscures bug-reporting buffer (!)
Date: Sun, 27 Dec 2015 10:00:48 -0800 (PST) [thread overview]
Message-ID: <9fc49264-f41a-47d3-8a62-5cdcdf37eeea@default> (raw)
In-Reply-To: <56801A87.7050107@gmx.at>
> I have no opinion other than that fixing this particular problem
by just removing other windows
> might introduce problems for people who would, for example, like
> to write a report based on the appearance of text shown in a
> particular window. If we deliberately delete such a window before
> the user is able to fill in the text for the report, she may have
> a hard time recreating it.
Exactly! And the same for *Completions*.
> And obviously deleting all other windows will be silly when the bug
> report window should pop up on a new frame anyway. Note in this
> context: We don't know beforehand whether that will happen!
Agreed, again.
> So to be sure: Does the present report warrant the proposed solution?
The right solution is _not_ to remove other windows.
Perhaps the right solution is to pop up a separate frame.
Or perhaps the "instructions" window should be combined with
the "report" window. Or perhaps the pre-Emacs 23 code could
serve as a guide (dunno).
next prev parent reply other threads:[~2015-12-27 18:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 23:21 bug#10873: 24.0.93; `report-emacs-bug' obscures bug-reporting buffer (!) Drew Adams
2012-09-17 0:10 ` Drew Adams
2014-02-09 5:11 ` Lars Ingebrigtsen
2014-02-11 14:33 ` Drew Adams
2015-12-25 23:34 ` Drew Adams
2015-12-26 9:36 ` Eli Zaretskii
2015-12-27 16:05 ` martin rudalics
2015-12-27 16:12 ` martin rudalics
2015-12-27 16:25 ` Eli Zaretskii
2015-12-27 16:57 ` Drew Adams
2015-12-27 17:16 ` Eli Zaretskii
2015-12-27 17:06 ` martin rudalics
2015-12-27 17:15 ` Eli Zaretskii
2015-12-27 18:00 ` Drew Adams
2015-12-27 18:37 ` martin rudalics
2015-12-27 19:14 ` Drew Adams
2015-12-28 10:08 ` martin rudalics
2015-12-27 18:36 ` martin rudalics
2015-12-28 18:23 ` martin rudalics
2015-12-28 18:35 ` Eli Zaretskii
2016-04-28 13:47 ` Lars Ingebrigtsen
2015-12-27 18:00 ` Drew Adams [this message]
2015-12-27 16:51 ` Drew Adams
2015-12-27 17:06 ` martin rudalics
2015-12-27 18:00 ` Drew Adams
2015-12-27 18:37 ` martin rudalics
2015-12-27 19:14 ` Drew Adams
2015-12-28 10:08 ` martin rudalics
2015-12-28 10:44 ` Drew Adams
2015-12-28 18:23 ` martin rudalics
2015-12-28 18:41 ` Drew Adams
[not found] ` <<43f2b0b2-fafc-43a9-b56a-120b90878cbc@default>
[not found] ` <<838u4hk0um.fsf@gnu.org>
[not found] ` <<56800C2E.80300@gmx.at>
[not found] ` <<83bn9bhna2.fsf@gnu.org>
[not found] ` <<1cf60229-6b8c-4c53-96f2-1b8f5d74b80b@default>
[not found] ` <<8337unhkwt.fsf@gnu.org>
2015-12-27 18:00 ` Drew Adams
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=9fc49264-f41a-47d3-8a62-5cdcdf37eeea@default \
--to=drew.adams@oracle.com \
--cc=10873@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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 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).