From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: with-standard-io-syntax Date: Wed, 22 Aug 2012 13:48:43 -0400 Message-ID: References: <87sjbgqply.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1345657736 17201 80.91.229.3 (22 Aug 2012 17:48:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 22 Aug 2012 17:48:56 +0000 (UTC) Cc: emacs-devel@gnu.org To: sds@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 22 19:48:54 2012 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 1T4F2z-000829-Cu for ged-emacs-devel@m.gmane.org; Wed, 22 Aug 2012 19:48:53 +0200 Original-Received: from localhost ([::1]:42779 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T4F2x-0002dN-Sv for ged-emacs-devel@m.gmane.org; Wed, 22 Aug 2012 13:48:51 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:35291) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T4F2u-0002Z7-Ng for emacs-devel@gnu.org; Wed, 22 Aug 2012 13:48:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T4F2t-000446-NA for emacs-devel@gnu.org; Wed, 22 Aug 2012 13:48:48 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:16018) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T4F2t-00043c-Im; Wed, 22 Aug 2012 13:48:47 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EAG6Zu09MCpcJ/2dsb2JhbABEtBGBCIIVAQEEAVYjBQsLNBIUGA2IQAW6CY0mgx4DozOBWIMF X-IronPort-AV: E=Sophos;i="4.75,637,1330923600"; d="scan'208";a="196452845" Original-Received: from 76-10-151-9.dsl.teksavvy.com (HELO pastel.home) ([76.10.151.9]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 22 Aug 2012 13:48:44 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 37D0258EB4; Wed, 22 Aug 2012 13:48:43 -0400 (EDT) In-Reply-To: <87sjbgqply.fsf@gnu.org> (Sam Steingold's message of "Tue, 21 Aug 2012 10:36:09 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 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:152754 Archived-At: > The introduction of print-length and print-level requires the CL-like > macro with-standard-io-syntax which would bind these (and all the future > variables which break read-back consistency) to nil. > Right now, (rgrep "print-length nil" "*.el" "~/src/emacs/trunk/" nil) > produces two dozen places where print-length is bound to nil and a quick > examination shows that the set of variable which need to be bound to nil > for print-read consistency is not uniformly understood. > I already have been bitten by this, and I think others will be sooner > rather than later. We could/should probably ignore print-length when print-circle is non-nil. Stefan