unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>, 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: Mon, 28 Dec 2015 11:08:01 +0100	[thread overview]
Message-ID: <56810A01.3060609@gmx.at> (raw)
In-Reply-To: <d4807142-5368-4448-8210-93ae93cc02d4@default>

 >> I consider the window showing *Completions* modal.
 >
 > That's clear.  But what is your reason (evidence) for saying
 > that.

That if you don't consider the window modal you will run into all sorts
of problems like the one that is the subject of this thread.  I'll give
you a more realistic scenario.  Assume that you have a directory ~/foo/
with two files say foo1 and foo2 and a directory ~/bar/ with two files
say bar1 and bar2.  Now do

emacs -Q

M-x customize-option RET abbrev-file-name RET

Put ~/foo/ into the editable field, point at its end and do

M-x widget-complete RET

Now do

C-x 5 2

M-x customize-option RET custom-file RET

Select "File", put ~/bar/ into the editable field, point at its end and
do

M-x widget-complete RET

again.  Note that at this moment you have changed the contents of the
*Completions* windows in _both_ frames.  If you now return to the first
frame and select a completion like bar1, nothing will happen (in the
best case).

This is the same cockpit error as the one from your scenario:
*Completions* windows are modal and should be treated accordingly, that
is, nicely.

 > Ah, so that's what you mean by "modal window".  Not that a user
 > is prevented from doing something else than interact with it,

A user is allowed to do something else as long as she behaves nicely.
That's the price she has to pay for not being "prevented from doing
something else than interact with it".  The user in the scenario above
does not behave nicely and neither do you when you want to report a bug
while the *Completions* windows is shown.  Such users are punished.

 > but that (a) it remains visible until (b) it is no longer needed,
 > when it disappears.
 >
 > That is not the usual meaning of "modal", but OK, good to know.
 >
 > I imagine that (a) is unnecessary, unless you are suggesting
 > that a user cannot remove such a window.  I'm guessing that
 > you perhaps mean, by (a), that no other automatically displayed
 > window takes its place, and that it is not otherwise removed
 > automatically.

All assumptions are off when you violate (a) or (b).

martin





  reply	other threads:[~2015-12-28 10:08 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
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 [this message]
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=56810A01.3060609@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 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).