all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: martin rudalics <rudalics@gmx.at>
Cc: 33498@debbugs.gnu.org
Subject: bug#33498: 26.1; Unable to delete minibuffer-only+child frames
Date: Wed, 6 Mar 2019 11:07:14 -0800	[thread overview]
Message-ID: <5c5d4a99-2b3f-785b-82f8-2ba5fb6da6cc@cs.ucla.edu> (raw)
In-Reply-To: <8736rpfklv.fsf@hochschule-trier.de>

[-- Attachment #1: Type: text/plain, Size: 581 bytes --]

> I think I fixed this now on master.  Please have a look.

Unfortunately the fix broke builds configured with
--enable-gcc-warnings, as GCC complains about the use of an
uninitialized variable that appears to be a typo in the fix. I installed
the attached patch to unbreak the build; please check it to make sure
that I understood the intent of the fix correctly.

It's a good idea to use './configure --enable-gcc-warnings' when making
changes to the C code in Emacs, as GCC is reasonably good at catching
typos like this, and typically does not generate too many false alarms.


[-- Attachment #2: 0001-Fix-typo-in-fix-for-Bug-33498.patch --]
[-- Type: text/x-patch, Size: 849 bytes --]

From 62879cbeae0221033a40d9f66e08673e4975e332 Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Wed, 6 Mar 2019 11:04:57 -0800
Subject: [PATCH] Fix typo in fix for Bug#33498

* src/frame.c (delete_frame): Fix typo in previous patch,
which caused GCC to complain about the use of an uninitialized
variable.
---
 src/frame.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/frame.c b/src/frame.c
index 3d83dc0a0d..1219569068 100644
--- a/src/frame.c
+++ b/src/frame.c
@@ -2236,7 +2236,7 @@ delete_frame (Lisp_Object frame, Lisp_Object force)
 		     for at least one other frame - so make it visible
 		     and quit.  */
 		  if (!FRAME_VISIBLE_P (f1) && !FRAME_ICONIFIED_P (f1))
-		    Fmake_frame_visible (frame1);
+		    Fmake_frame_visible (minibuffer_child_frame);
 
 		  return Qnil;
 		}
-- 
2.20.1


  parent reply	other threads:[~2019-03-06 19:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-25 11:43 bug#33498: 26.1; Unable to delete minibuffer-only+child frames Andreas Politz
2018-11-25 17:40 ` martin rudalics
2018-11-25 18:28   ` Andreas Politz
2018-11-25 18:57     ` martin rudalics
2018-11-25 19:33       ` Andreas Politz
2018-11-26  9:31         ` martin rudalics
2018-11-26 18:59           ` Andreas Politz
2018-11-27 10:14             ` martin rudalics
2019-03-05 10:12 ` martin rudalics
2019-03-13 20:24   ` Andreas Politz
2019-04-23  8:46     ` martin rudalics
2019-03-06 19:07 ` Paul Eggert [this message]
2019-03-07  8:28   ` 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

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

  git send-email \
    --in-reply-to=5c5d4a99-2b3f-785b-82f8-2ba5fb6da6cc@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=33498@debbugs.gnu.org \
    --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 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.