From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: bug-gnu-emacs@gnu.org, juergen.fenn@GMX.DE
Subject: Re: No Windows File Dialogue in Win98SE
Date: Mon, 11 Jun 2007 23:05:30 +0300 [thread overview]
Message-ID: <ubqfmjlyt.fsf@gnu.org> (raw)
In-Reply-To: <466CE32C.4050703@gmx.at> (message from martin rudalics on Mon, 11 Jun 2007 07:52:44 +0200)
> Date: Mon, 11 Jun 2007 07:52:44 +0200
> From: martin rudalics <rudalics@gmx.at>
> Cc: bug-gnu-emacs@gnu.org, Juergen Fenn <juergen.fenn@GMX.DE>
>
> (I apologize for not noticing this before but I try to avoid
> these dialogs whenever I can.)
FWIW, I've developed a minimal ``sanity check'' type of procedure to
test that a freshly built Emacs doesn't have any grave bugs in its GUI
features:
. click menu bar, make sure menus open and tooltip help for menu
items pops up and down;
. move mouse pointer above tool-bar buttons, make sure they sense the
mouse and that tooltip help pops up and down;
. click File->Open File and File-Open Directory, make sure the file
and directory selectors pop up;
. same with tool-bar Open File and Open Directory buttons;
. move mouse pointer above mode line, make sure it senses the mouse
and that tooltip help pops up and down;
. click mouse-3 in the text area, make sure context menu pops up and
down;
. click mouse-3 on the mode line where the mode name is displayed,
make sure the minor mode menu pops up;
. press S-mouse-1, make sure the font selector pops up;
. click Help->Read the Emacs manual, and make sure that mouse
highlight on menu items and cross-references works
next prev parent reply other threads:[~2007-06-11 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 20:40 No Windows File Dialogue in Win98SE Juergen Fenn
2007-06-10 23:27 ` Jason Rumney
2007-06-11 5:52 ` martin rudalics
2007-06-11 7:54 ` Jason Rumney
2007-06-11 20:05 ` Eli Zaretskii [this message]
2007-06-11 20:31 ` Juergen Fenn
2007-06-11 22:17 ` Jason Rumney
2007-06-12 19:58 ` Juergen Fenn
2007-06-14 6:59 ` martin rudalics
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=ubqfmjlyt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=juergen.fenn@GMX.DE \
--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).