From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: 23.0.50; savehist save invalid syntax Date: Tue, 04 Sep 2007 23:20:10 -0400 Message-ID: References: <59217.128.165.123.18.1188946127.squirrel@webmail.lanl.gov> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1188963040 15267 80.91.229.12 (5 Sep 2007 03:30:40 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 5 Sep 2007 03:30:40 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, rms@gnu.org, Leo To: herring@lanl.gov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 05 05:30:40 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1ISlbB-0005j0-Vq for ged-emacs-devel@m.gmane.org; Wed, 05 Sep 2007 05:30:38 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ISlbA-0003zF-DQ for ged-emacs-devel@m.gmane.org; Tue, 04 Sep 2007 23:30:36 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ISlaV-000346-8f for emacs-devel@gnu.org; Tue, 04 Sep 2007 23:29:55 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ISlaQ-0002xn-9p for emacs-devel@gnu.org; Tue, 04 Sep 2007 23:29:54 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ISlaP-0002xM-On for emacs-devel@gnu.org; Tue, 04 Sep 2007 23:29:49 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1ISlaO-0003w4-Ty for emacs-devel@gnu.org; Tue, 04 Sep 2007 23:29:49 -0400 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1ISla8-0006Lz-MU for emacs-pretest-bug@gnu.org; Tue, 04 Sep 2007 23:29:32 -0400 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1ISlR6-0001pZ-8t for emacs-pretest-bug@gnu.org; Tue, 04 Sep 2007 23:20:15 -0400 Original-Received: from tomts13.bellnexxia.net ([209.226.175.34] helo=tomts13-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1ISlR5-0001pC-Fq; Tue, 04 Sep 2007 23:20:11 -0400 Original-Received: from pastel.home ([70.53.192.250]) by tomts13-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20070905032010.OHWM13659.tomts13-srv.bellnexxia.net@pastel.home>; Tue, 4 Sep 2007 23:20:10 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 6BF8E8010; Tue, 4 Sep 2007 23:20:10 -0400 (EDT) In-Reply-To: <59217.128.165.123.18.1188946127.squirrel@webmail.lanl.gov> (Davis Herring's message of "Tue\, 4 Sep 2007 15\:48\:47 -0700 \(PDT\)") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/23.0.50 (gnu/linux) X-Detected-Kernel: Solaris 8 (1) X-Detected-Kernel: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:77816 gmane.emacs.pretest.bugs:19742 Archived-At: >> I think the best approach is to discard any element of command-history >> that contains anything unreadable. If the arguments of a command >> include a mouse event, repeating it in another session won't make much >> sense anyway. > With this much complexity, my temptation would be to provide a > print-readable function (or an optional argument to an existing printer) > that signalled if it were asked to print something that has no read > syntax. Of course, this could be done in Lisp by recursively checking the > type of every element of every sequence, but that would traverse the tree > twice and would fail on circular structures unless `print-circle' were > duplicated within it. Agreed, except that rather than failing, the function should call a callback which could choose to print those failed elements in some way (or to signal an error). Stefan