From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Davis Herring" Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: RE: 23.0.50; savehist save invalid syntax Date: Mon, 10 Sep 2007 17:55:04 -0700 (PDT) Message-ID: <25364.128.165.0.81.1189472104.squirrel@webmail.lanl.gov> References: Reply-To: herring@lanl.gov NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1189473813 24345 80.91.229.12 (11 Sep 2007 01:23:33 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 11 Sep 2007 01:23:33 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 11 11:23:20 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 1IV1WY-0002XO-UO for ged-emacs-devel@m.gmane.org; Tue, 11 Sep 2007 10:55:11 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IUu2C-0007vE-9O for ged-emacs-devel@m.gmane.org; Mon, 10 Sep 2007 20:55:20 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IUu29-0007sr-1Y for emacs-devel@gnu.org; Mon, 10 Sep 2007 20:55:17 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IUu28-0007sQ-Fa for emacs-devel@gnu.org; Mon, 10 Sep 2007 20:55:16 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IUu28-0007sE-CP for emacs-devel@gnu.org; Mon, 10 Sep 2007 20:55:16 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IUu27-0008R3-Su for emacs-devel@gnu.org; Mon, 10 Sep 2007 20:55:16 -0400 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IUu1k-0003g0-Bk for emacs-pretest-bug@gnu.org; Mon, 10 Sep 2007 20:54:52 -0400 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1IUu24-0008QH-OZ for emacs-pretest-bug@gnu.org; Mon, 10 Sep 2007 20:55:15 -0400 Original-Received: from mailwasher.lanl.gov ([192.65.95.54] helo=mailwasher-b.lanl.gov) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IUu24-0008Q3-5b for emacs-pretest-bug@gnu.org; Mon, 10 Sep 2007 20:55:12 -0400 Original-Received: from mailrelay2.lanl.gov (mailrelay2.lanl.gov [128.165.4.103]) by mailwasher-b.lanl.gov (8.13.8/8.13.6/(ccn-5)) with ESMTP id l8B0t94n017065; Mon, 10 Sep 2007 18:55:09 -0600 Original-Received: from webmail1.lanl.gov (webmail1.lanl.gov [128.165.4.106]) by mailrelay2.lanl.gov (8.13.8/8.13.8/(ccn-5)) with ESMTP id l8B0t5KO013406; Mon, 10 Sep 2007 18:55:05 -0600 Original-Received: from webmail1.lanl.gov (localhost.localdomain [127.0.0.1]) by webmail1.lanl.gov (8.12.11.20060308/8.12.11) with ESMTP id l8B0t5p1010551; Mon, 10 Sep 2007 18:55:05 -0600 Original-Received: (from apache@localhost) by webmail1.lanl.gov (8.12.11.20060308/8.12.11/Submit) id l8B0t49Z010549; Mon, 10 Sep 2007 17:55:04 -0700 X-Authentication-Warning: webmail1.lanl.gov: apache set sender to herring@lanl.gov using -f Original-Received: from 128.165.0.81 (SquirrelMail authenticated user 196434) by webmail.lanl.gov with HTTP; Mon, 10 Sep 2007 17:55:04 -0700 (PDT) In-Reply-To: User-Agent: SquirrelMail/1.4.8-6.el3.2lanl X-Priority: 3 (Normal) Importance: Normal X-CTN-5-MailScanner-Information: Please see http://network.lanl.gov/email/virus-scan.php X-CTN-5-MailScanner: Found to be clean X-CTN-5-MailScanner-From: herring@lanl.gov X-Detected-Kernel: Linux 2.4-2.6 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:78543 gmane.emacs.pretest.bugs:19839 Archived-At: > The newlines are not necessary, unless you're thinking of someone viewing > .emacs-history. That is, any whitespace will do. I used a space, but a > newline is OK too. If we don't care what the file looks like, lots of things become optional: (setq foo'bar) works, for instance. I thought I'd err on the side of readability. > In that case, you might want to comment the Lisp code to that effect. It's > not very obvious that a Lisp reader error could be raised by `prin1'. And > I > think it's probably still better to leave the general `error' handler. I think the documentation for the (new) variable `print-unreadable-function' may be sufficient, but I could add one. I specifically don't want to catch all errors there, because any other error ought to be noticed, not suppressed. > What Lisp value can I test for [the new print feature]? It's obviously not > `emacs-major-version' >= 22. Is there a featurep or fboundp or boundp I > can test? If not, is there a minor version I can test? If I can't find > something to test, then I'll have to leave the `read' in for new Emacs > versions also, which is obviously a waste. You can, outside the `let', test (boundp 'print-unreadable-function). You can also test >= 22.2, if it's added there, or >= 23 otherwise (CVS has such a version). > Do as you think best. The doc string suggests that a decimal value is > used, so I used one. Also, I think decimal is what will be used by most > users in Customize. That is, even if one can enter #o600 in the Customize > editable field, I doubt that most users will think to do that. To me, the > doc string helps in this regard, and a decimal default value helps. I > don't see a real benefit in using octal here, but that's just my opinion. Once read, there is no difference between #o600 and 384; there are no "octal integers", only octal integer literals. The user never sees it, then, and it has no effect on Customize. The doc string is simply reminding you that the value is the true mode value, and not some decimal-interpreted-as-octal trick where six hundred sixty means rw-rw---- (and eighty has no meaning at all). > OK. As I say, I don't recall the specific need. I do recall that it was > preventing one from quitting Emacs, because `savehist-autosave' is in > `kill-emacs-hook' (as well as on a timer). That is, if, for any reason, it > has a problem, then it gets in the way of exiting. That was what was > happening, but perhaps that problem will never arise in the future ;-). I wonder why `kill-emacs-hook' is allowed to stop Emacs exiting; if a function on it signals, shouldn't one just proceed to the next function or to the actual exit? It's not supposed to be able to veto exiting; that's what `kill-emacs-query-functions' is for. Davis -- This product is sold by volume, not by mass. If it appears too dense or too sparse, it is because mass-energy conversion has occurred during shipping.