From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: Leaving out non-applicable commands on Mx Date: Fri, 8 Jan 2016 19:09:04 -0800 (PST) Message-ID: References: <87mvszdp6b.fsf@gnus.org> <8737u9kv6f.fsf@russet.org.uk> <87fuy7hdc6.fsf_-_@wanadoo.es> <87bn8vh8q4.fsf@wanadoo.es> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1452308971 17319 80.91.229.3 (9 Jan 2016 03:09:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 9 Jan 2016 03:09:31 +0000 (UTC) Cc: emacs-devel@gnu.org To: John Wiegley , =?utf-8?B?w5NzY2FyIEZ1ZW50ZXM=?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 09 04:09:18 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aHju2-0003Bk-83 for ged-emacs-devel@m.gmane.org; Sat, 09 Jan 2016 04:09:18 +0100 Original-Received: from localhost ([::1]:38787 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHju1-0001xt-8W for ged-emacs-devel@m.gmane.org; Fri, 08 Jan 2016 22:09:17 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53460) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHjtx-0001uj-2q for emacs-devel@gnu.org; Fri, 08 Jan 2016 22:09:14 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aHjts-000579-41 for emacs-devel@gnu.org; Fri, 08 Jan 2016 22:09:13 -0500 Original-Received: from aserp1040.oracle.com ([141.146.126.69]:23537) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHjtr-00056r-Ts; Fri, 08 Jan 2016 22:09:08 -0500 Original-Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u09396Rp024666 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 9 Jan 2016 03:09:06 GMT Original-Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0022.oracle.com (8.13.8/8.13.8) with ESMTP id u09395rF026636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 9 Jan 2016 03:09:06 GMT Original-Received: from abhmp0013.oracle.com (abhmp0013.oracle.com [141.146.116.19]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u09395Uq009526; Sat, 9 Jan 2016 03:09:05 GMT In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6691.5000 (x86)] X-Source-IP: userv0022.oracle.com [156.151.31.74] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 141.146.126.69 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:197870 Archived-At: > I sense ways in which this could go wrong: expecting to find > a command, failing for some undiscovered reason X, and then > the user believing no such command exists. Yes. And from the outset the user will have only a restricted view of what commands are currently available, because an Emacs developer will have made a priori assumptions about which commands are currently appropriate. If that's really important for some specific mode then it is easy enough to implement that for a given mode. It should not be imposed on all of Emacs (e.g., via `M-x'). The specific command reading input should filter as is appropriate for it, using a predicate - as has always been the case. And (IMHO), no such filter is appropriate for `M-x', which should remain general. Of course, nothing prevents someone from defining a command similar to `M-x' but that is more restrictive in the sense suggested (simple to do). Just please don't bind it by default to `M-x'. > Core Emacs behavior doesn't need to change to demonstrate this > feature, does it? Write a new execute-extended-command and see > if it works as well as you hope. Precisely (only please don't call it `execute-extended-command' ;-)).