--- Begin Message ---
Subject: |
25.0.50; Error when click window-mgr icon to close window (frame) and quit Emacs |
Date: |
Wed, 22 Oct 2014 08:26:11 -0700 (PDT) |
emacs -Q -nw
Click the tiny X icon in the upper right of the frame, to close the
frame and thus quit Emacs. You get a popup MS Windows dialog:
GNU Emacs: The extensible self-documenting text editor has stopped
working
A problem caused the program to stop working correctly. Please close the
program.
--> Close the program
Clicking `Close the program' then closes the program. This error dialog
box should not appear at all - Emacs should just close.
In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
of 2014-10-06 on LEG570
Bzr revision: 118063 address@hidden
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking=yes,glyphs 'CFLAGS=-O0 -g3'
CPPFLAGS=-DGLYPH_DEBUG=1'
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#18795: 25.0.50; Error when click window-mgr icon to close window (frame) and quit Emacs |
Date: |
Wed, 22 Oct 2014 19:38:17 +0300 |
> Date: Wed, 22 Oct 2014 18:28:35 +0200
> From: Dani Moncayo <address@hidden>
> Cc: Drew Adams <address@hidden>, address@hidden
>
> >> emacs -Q -nw
> >>
> >> Click the tiny X icon in the upper right of the frame, to close the
> >> frame and thus quit Emacs. You get a popup MS Windows dialog:
> >>
> >> GNU Emacs: The extensible self-documenting text editor has stopped
> >> working
> >>
> >> A problem caused the program to stop working correctly. Please close the
> >> program.
> >
> > Not reproducible with today's trunk.
> >
> >> In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
> >> of 2014-10-06 on LEG570
> >
> > This is 2 weeks old, so perhaps the problem was already fixed.
> >
> > Can someone else reproduce this with a recent trunk?
>
> I just tried with:
>
> GNU Emacs 25.0.50.1 (i686-pc-mingw32)
> of 2014-10-20 on LEG570
> Copyright (C) 2014 Free Software Foundation, Inc.
>
> on a Windows 7 machine, and the cmd console window closes normally,
> without any popup dialog.
Thanks, then I guess we can close this bug.
--- End Message ---