From xemacs-m  Wed Jul  9 06:01:45 1997
Received: from chaos.hut.fi (ave@chaos.hut.fi [130.233.244.36])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id GAA08530
	for <xemacs-beta@xemacs.org>; Wed, 9 Jul 1997 06:01:45 -0500 (CDT)
Received: (from ave@localhost)
	by chaos.hut.fi (8.8.5/8.8.5) id OAA15140;
	Wed, 9 Jul 1997 14:03:11 +0300
To: xemacs-beta@xemacs.org
Subject: Re: [patch] File->Delete Frame sensitivity
References: <l2en99mi2s.fsf@chaos.hut.fi> <by4ta4smgi.fsf@midget.math.ethz.ch>
Mail-Copies-To: never
X-Attribution: Ave
From: Aki Vehtari <Aki.Vehtari@hut.fi>
In-Reply-To: Jan Vroonhof's message of "09 Jul 1997 09:39:57 +0200"
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
Date: 09 Jul 1997 14:03:10 +0300
Message-ID: <l2bu4cmqs1.fsf@chaos.hut.fi>
Lines: 25
X-Mailer: Gnus v5.4.60/XEmacs 20.3(beta10) - "Athens"


 "Jan" == Jan Vroonhof <vroonhof@math.ethz.ch> writes:
 Jan> One should probably make sure whether it uses the same
 Jan> logic as delete-frame uses internally.

Yes, it shouldn't count minibuffer-only frames.
But should it count tty frames? And what is difference
with console-types 'x and 'window-system?

With this patch, it counts all  frames on window-system consoles
excluding minibuffer-only frames. Tested with X.


--- x-menubar.el.orig   Wed Jul  9 13:59:08 1997
+++ x-menubar.el        Wed Jul  9 13:57:18 1997
@@ -779,7 +779,9 @@
                 (aset item 2 (not (not (or buffer-file-name
                                            revert-buffer-function)))))
            (and (string= "Delete Frame" name)
-                (aset item 2 (device-or-frame-p (second (frame-list)))))
+                (aset item 2 (not (eq (next-frame (selected-frame)
+                                                  'nomini 'window-system)
+                                      (selected-frame)))))
            )))
     result))

