all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
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 17:05:02 +0100	[thread overview]
Message-ID: <56800C2E.80300@gmx.at> (raw)
In-Reply-To: <838u4hk0um.fsf@gnu.org>

 >> This bug is still 100% reproducible in an Emacs 25 build of 2015-12-10:
 >
 > Martin, could you please look into this?

There's not much I can do about this.  I can give a simpler recipe with
emacs -Q: Type C-h f set- RET and see the *Completions* window pop up.
Then type M-x report-emacs-bug.

OT1H the window showing the *Completions* buffer is softly dedicated to
that buffer.  This is necessary to make sure that an intermittent
‘display-buffer’ does not steal that window for showing another buffer.
Windows showing *Completions* should disappear immediately when they are
no more needed but till then they should be continuously visible.

OTOH ‘report-emacs-bug’ apparently assumes that it always has two
windows at its disposal - one for the message and one for help.  This
assumption misfires with the recipe at hand.  (Note that my machine in
addition also displays a warning from ‘compose-mail’ which gets usually
immediately buried when showing either the message or the help.)

IMO this report is the result of a cockpit error.  As long as a "modal"
window like that showing *Completions* is open, users should not start
an unrelated activity, including that of writing a bug report.

If, however, people think that ‘report-emacs-bug’ should always succeed
showing both of its windows in every conceivable context, we can do that
easily by calling ‘delete-other-windows’ before ‘display-buffer’.  This
will clearly misfire for people showing more than two windows per frame.

So it's your choice ...

martin






  reply	other threads:[~2015-12-27 16:05 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=56800C2E.80300@gmx.at \
    --to=rudalics@gmx.at \
    --cc=10873@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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 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.