From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 16636-done@debbugs.gnu.org
Subject: bug#16636: 24.3.50; REGRESSION: y/n file dialog is only flashed; input is not read
Date: Tue, 04 Feb 2014 18:21:23 +0200 [thread overview]
Message-ID: <838utq3l30.fsf@gnu.org> (raw)
In-Reply-To: <1af9fb2e-0ce0-430a-a9ee-b13838b88047@default>
> Date: Mon, 3 Feb 2014 20:07:26 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
>
> emacs -Q
>
> Eval this after bring up Dired:
>
> (defun diredp-mouse-find-file-other-frame (event)
> (interactive "e")
> (let ((pop-up-frames t)) (dired-mouse-find-file-other-window event)))
>
> (define-key dired-mode-map [M-mouse-2] 'diredp-mouse-find-file-other-frame)
>
> In another Emacs session, modify one of the files listed in the Dired
> buffer. Then click M-mouse-2 on it in the Dired buffer.
>
> In my own setup I at least see a brief flash of a message. I see
> nothing at all happen with emacs -Q.
You should hear the "ding" that is sounded when you type C-g or
dismiss a menu. (And the file in question should have been already
visited inside Emacs before the "in another Emacs session" step,
otherwise Emacs has no need to display any dialogs.)
> I look in *Messages* but nothing is recorded there ("normal").
You should see "Quit" there, which is a sign that none of the possible
selections were chosen, i.e. the dialog was dismissed without making a
selection.
> There should have been a file dialog displayed, and it should have
> waited for me to click y or n to dismiss it.
>
> Do `M-x debug-on-entry diredp-mouse-find-file-other-frame', then repeat:
> click `M-mouse-2' on the same (modified) file. Walk through the
> debugger and you will see the file dialog displayed as it should be
Displayed, yes. But not "as it should be": the appearance is entirely
different, as Emacs tried to emulate a dialog box with a menu. But
for a "simple dialog" such as yes/no, Emacs should have displayed a
MessageBox instead.
Sorry, this was my bad: some code which supported this use case was
inadvertently deleted when the TTY menus were implemented.
Now fixed in trunk revision 116260.
next prev parent reply other threads:[~2014-02-04 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 4:07 bug#16636: 24.3.50; REGRESSION: y/n file dialog is only flashed; input is not read Drew Adams
2014-02-04 16:21 ` Eli Zaretskii [this message]
[not found] <<1af9fb2e-0ce0-430a-a9ee-b13838b88047@default>
[not found] ` <<838utq3l30.fsf@gnu.org>
2014-02-04 16:30 ` Drew Adams
2014-02-04 18:21 ` Eli Zaretskii
[not found] ` <<9567eef7-8d7e-405c-a656-faefe34c9991@default>
[not found] ` <<831tzi3fje.fsf@gnu.org>
2014-02-04 18:51 ` Drew Adams
2014-02-04 19:20 ` Eli Zaretskii
[not found] <<f6441b2f-6aa7-44eb-b88c-ebcb4764fc49@default>
[not found] ` <<83wqha1y88.fsf@gnu.org>
2014-02-04 21:03 ` 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=838utq3l30.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16636-done@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).