From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.help Subject: RE: How the backquote and the comma really work? Date: Thu, 25 Jun 2015 13:37:31 -0700 (PDT) Message-ID: <426839d6-b4e9-4ed9-9793-1cf9c942e831@default> References: <87vbebg1fs.fsf@mbork.pl> <1e190a42-19c5-4755-b263-4334c402619a@default> <877fqrbpij.fsf@web.de> <87ioabfwm7.fsf@mbork.pl> <87mvzn37cq.fsf@web.de> <87fv5ffsnx.fsf@mbork.pl> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1435264688 29590 80.91.229.3 (25 Jun 2015 20:38:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 25 Jun 2015 20:38:08 +0000 (UTC) To: Marcin Borkowski , Michael Heerdegen , help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Jun 25 22:37:56 2015 Return-path: Envelope-to: geh-help-gnu-emacs@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 1Z8DuE-0007zs-Fq for geh-help-gnu-emacs@m.gmane.org; Thu, 25 Jun 2015 22:37:54 +0200 Original-Received: from localhost ([::1]:57393 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z8DuD-0003Pq-So for geh-help-gnu-emacs@m.gmane.org; Thu, 25 Jun 2015 16:37:53 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35976) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z8Du1-0003Pk-Fy for help-gnu-emacs@gnu.org; Thu, 25 Jun 2015 16:37:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z8Dtw-0005FF-BF for help-gnu-emacs@gnu.org; Thu, 25 Jun 2015 16:37:41 -0400 Original-Received: from aserp1040.oracle.com ([141.146.126.69]:20029) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z8Dtw-0005Ek-4v for help-gnu-emacs@gnu.org; Thu, 25 Jun 2015 16:37:36 -0400 Original-Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t5PKbWNJ013155 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 25 Jun 2015 20:37:33 GMT Original-Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserv0021.oracle.com (8.13.8/8.13.8) with ESMTP id t5PKbW8s019577 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 25 Jun 2015 20:37:32 GMT Original-Received: from abhmp0015.oracle.com (abhmp0015.oracle.com [141.146.116.21]) by userv0122.oracle.com (8.13.8/8.13.8) with ESMTP id t5PKbV7U022298; Thu, 25 Jun 2015 20:37:32 GMT In-Reply-To: <87fv5ffsnx.fsf@mbork.pl> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6691.5000 (x86)] X-Source-IP: aserv0021.oracle.com [141.146.126.233] 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: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:105185 Archived-At: > >> pp binds `print-quoted' unconditionally to t when printing. >=20 > That's a pity. Not Emacs-y way of doing things, I guess; IMHO, the > Emacs-y way would be to bind print-quoted to pp-default-print- > quoted, set to t by default;-). Just `pp-print-quoted' - and yes, agreed; such a variable could have been provided and used. This is, for example, why library `pp+.el' offers the following options, as distinct from the ones that lack prefix `pp-': `pp-eval-expression-print-length' `pp-eval-expression-print-level' And it is why it uses `pp-read-expression-map' instead of `read-expression-map' (similar, but `pp-*' uses some Emacs-Lisp key bindings). Evaluating with pretty printing is generally a different use case from `eval-expression'. But I didn't think to provide a variable `pp-print-quoted' (or `pp-eval-expression-print-quoted'). It's not a common use case, but anyway, now you know. `eval-expression' and `pp-eval-expression' are just commands - nothing special. (The real gotcha comes when people mistakenly think that using them is tantamount to evaluating normally in all cases. These commands do more than just evaluate, including reading the sexp to evaluate and printing the result.)