From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: `read--expression' and `read-minibuffer' Date: Sat, 3 Sep 2016 22:53:01 -0700 (PDT) Message-ID: <60e5e890-6f50-4f38-a74f-e82ff83b24dc@default> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1472968406 12749 195.159.176.226 (4 Sep 2016 05:53:26 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 4 Sep 2016 05:53:26 +0000 (UTC) To: Stefan Monnier , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Sep 04 07:53:22 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bgQMr-0002jf-Ac for ged-emacs-devel@m.gmane.org; Sun, 04 Sep 2016 07:53:21 +0200 Original-Received: from localhost ([::1]:48850 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bgQMo-0002RF-1c for ged-emacs-devel@m.gmane.org; Sun, 04 Sep 2016 01:53:18 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40550) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bgQMh-0002Qu-Gi for emacs-devel@gnu.org; Sun, 04 Sep 2016 01:53:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bgQMc-0008DM-B8 for emacs-devel@gnu.org; Sun, 04 Sep 2016 01:53:10 -0400 Original-Received: from aserp1040.oracle.com ([141.146.126.69]:29055) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bgQMc-0008DI-3C for emacs-devel@gnu.org; Sun, 04 Sep 2016 01:53:06 -0400 Original-Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u845r4A0008708 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 4 Sep 2016 05:53:04 GMT Original-Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u845r31k018593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 4 Sep 2016 05:53:04 GMT Original-Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u845r1xB005975; Sun, 4 Sep 2016 05:53:02 GMT In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6753.5000 (x86)] X-Source-IP: userv0021.oracle.com [156.151.31.71] 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.21 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" Xref: news.gmane.org gmane.emacs.devel:207163 Archived-At: > > Well, sure, there are Lisp objects (e.g. byte-compiled > > functions) that are not readable expressions. But those are > > not readable anyway, AFAIK. >=20 > Lists of symbols are Lisp object, are perfectly readable, but shouldn't > use `read--expression'. I don't see why not. > `read--expression' is to read the subset of > S-exps which represent an Elisp expression (something that would be > meaningful to pass to `eval', for example). I don't see why you think that what it reads is limited, or could or should be limited, to expressions that can be eval'd. (read--expression "Expression: ") (1 2 frou frou) =3D> (1 2 frou frou) > > Why isn't `read--expression' treated as a user function, like > > `read-minibuffer', instead of being considered "internal"? >=20 > Can't remember the details, but I think it's because it's easier to make > it "external" than the reverse. How about making it external now? It is a useful general-purpose function. > > And `read-minibuffer' is still used for `interactive' with > > spec "x". Why isn't `read--expression' used for that now? >=20 > Not sure either. Probably just a conservative choice. Maybe consider it? I don't see any risk. The main difference is that it uses a more useful keymap for reading expressions.