From xemacs-m  Sat Jun 28 18:08:22 1997
Received: from piglet.splode.com (h-205-217-243-176.netscape.com [205.217.243.176])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id SAA20016
	for <xemacs-beta@xemacs.org>; Sat, 28 Jun 1997 18:08:21 -0500 (CDT)
Received: (from friedman@localhost)
	by piglet.splode.com (8.8.5/8.8.5) id PAA02498;
	Sat, 28 Jun 1997 15:47:25 -0700
Date: Sat, 28 Jun 1997 15:47:25 -0700
Message-Id: <199706282247.PAA02498@piglet.splode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Noah Friedman <friedman@splode.com>
To: kyle_jones@wonderworks.com
Cc: xemacs-beta@xemacs.org
Subject: [PATCH] teach-extended-commands-p change
Reply-To: friedman@splode.com
In-Reply-To: <kyle_jones@wonderworks.com> Mon, 23 Jun 1997 06:54:50 -0400
References: <kiglo41mzd5.fsf@jagor.srce.hr>
	<QQcvdz08657.199706231054@crystal.WonderWorks.COM>

> > ** The feature to suggest key bindings when you use M-x now operates
> > after the command finishes.  The message suggesting key bindings
> > appears temporarily in the echo area.  The previous echo area contents
> > come back after a few seconds, in case they contain useful information.
>
>The way ours works is intentional, if it is based on the code I
>wrote many years ago.  The idea is to report the key sequence
>that you could have typed, not the key sequence that you can now
>type after the command has potentially rejiggered the keymaps.

I don't see this as a big win.  Telling the user of a local keybinding
(whether that keybinding is in the local map before the command is run or
after it completes) is just as generally useless.  At least informing the
user afterward doesn't cause insufferable delays in the execution of the
command.

