From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: ken Newsgroups: gmane.emacs.help Subject: Re: desktop-read usage and syntax ::error, strange character :: half-SOLVED!!! Date: Tue, 18 Jul 2017 17:10:46 -0400 Message-ID: References: <6b820ba4-770c-1d87-7b4c-a582f1830dbb@mousecar.com> Reply-To: gebser@mousecar.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1500412295 17257 195.159.176.226 (18 Jul 2017 21:11:35 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 18 Jul 2017 21:11:35 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 To: GNU Emacs List Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jul 18 23:11:32 2017 Return-path: Envelope-to: geh-help-gnu-emacs@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 1dXZmD-00041A-Re for geh-help-gnu-emacs@m.gmane.org; Tue, 18 Jul 2017 23:11:30 +0200 Original-Received: from localhost ([::1]:58637 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dXZmF-0005Go-As for geh-help-gnu-emacs@m.gmane.org; Tue, 18 Jul 2017 17:11:31 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40722) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dXZlj-0005GY-QY for help-gnu-emacs@gnu.org; Tue, 18 Jul 2017 17:11:00 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dXZle-0007dh-RU for help-gnu-emacs@gnu.org; Tue, 18 Jul 2017 17:10:59 -0400 Original-Received: from mout.perfora.net ([74.208.4.194]:50143) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dXZle-0007cq-Ir for help-gnu-emacs@gnu.org; Tue, 18 Jul 2017 17:10:54 -0400 Original-Received: from nv.mousecar.net ([96.27.75.237]) by mrelay.perfora.net (mreueus002 [74.208.5.2]) with ESMTPSA (Nemesis) id 0M26jF-1dmlGh2LdL-00ty5y for ; Tue, 18 Jul 2017 23:10:52 +0200 In-Reply-To: Content-Language: en-US X-Provags-ID: V03:K0:+Z/RuSynAlX53BHo1S56VnG/KyHhBWAqHLg4BN+/1TP8xpqXwUZ wsbwTBPGOqySdhwkfROQEWefij2au/SbIjb6qed9kUr03J5Eyciouz5CRgz2bFM9oszYDtA qmPigvdU9IlnQil94dO0XBzGQ3Cb/nWrrnYv6SfB8xY4vR9e+1FO0t3FiHQBmEtMBI9DceF 6KqzhVsyT/m/Cnr74FHyg== X-UI-Out-Filterresults: notjunk:1;V01:K0:XDYaz4O6ctk=:bAOb5lAXld78IxAWbON+Gs lKEyq9uFJq0iGTjMqA6bEGBA0z24DehZ+x2fx73+v/j5W9qyPTbJYY1vLO5dVtyJ07EUT0JW9 s8cg9t6rxSRYKlmp+tLdIZA6pAC7z1eqZCNCS3zhQONOAGO0Ucy79WBkMJX+kn7PwIizJ6Uc5 UJJYVRx3soIox8nySk4ZEFNv1XWHe3XDPM+904vvI9BLG9IOVhwcEhULtDe/qjLOY7xJ1zHm5 G2R2vYTmGOvl4k+gapmF1/HV/dR6fZ6r7gR/s+PFAx06rjCsMAhc/1yCnQalY8EGt2GbZ177/ QB36h4VBvfPH0bVXXB3PLhslewviKmj3PB8S08fD78RRssDCI+RC3E229lyml5t5CfQY8yxod plFx7H3ONUua/5xUrWu0kYKtmCne7qS3dW2LUrsFJfFrVhixNftR1pQG2BUG/sgwVqNnY6zMd E0Rji8dnZk2SXzlbFpZaibw6Ye8vJLE7FM8bzjL6fg35ThztWYMO0yScz7LDiBmdYF/Nt+9io EEzYl+9gjNIfhXL8TJ0lWHE+s/vuDr7M0utC0jEtrioBDPHqTFZJxuOUGmFJh5O6XokL2apA4 DDtRh7ysZhD29fuezzh4MROQBSHML8bKV0RsdW9+vq3lSvcXClGuVnbIGcPMFtUmcu9q8tcYm lXFlaJguY4fr7yyQPz1AxW34zQ9qFIEz5ASAGZumMwwDydp6Tzt7HZmsoI9JcRSAppXgcsCjv Hujt6zOkuHiqfgEV4yqDtxeold3DSKP8RHWkyQuDcDkIKkAB3jWRd50r00A= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 74.208.4.194 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.help:113783 Archived-At: On 07/18/2017 03:59 PM, John Mastro wrote: > ken wrote: >> For some reason, when booting after a crash, the desktop isn't loaded; >> that is, the files which were loaded in the previous (crashed) session >> aren't loaded again. I suspected this was due to >> "~/.emacs/.emacs.desktop.lock", so I deleted it. Then I close emacs >> and start it again, but still the desktop isn't loaded. >> >> So then I try to load it by hand, ie, I run "M-x desktop-read"... this >> yields the error: "eval-buffer: Symbol's value as variable is void: >> Î". Yes, the last character is a capital "I" with a carot above it. >> If, from the "*scratch*" buffer I run (desktop-read >> "/home/user/.emacs.d/"), I get exactly the same error message. > I can't offer any specific help, but if your desktop file is corrupted > (which is what it sounds like), it's probably worth reporting that as a > bug. Perhaps that's can't be reasonably avoided after a crash, but > perhaps it can, and the Emacs developers would know best. > > John Yeah, that's pretty vague... I'd think the people fielding bug reports would toss such a report without a lot more to help track it down. However, you were spot on. Here's the deal: Most of the info in .emacs.desktop is inscrutable... I don't know what the bejesus it is. I even saw a bunch of lines like this: > (desktop-create-buffer <81> (81x = 129d ; CEx = 206d !!!) and didn't think it terribly odd. But then I compared that file to one of the backups I have of previous versions of the same file and, instead of the "<81>", there was "206"... in every case. So I did a search-and-replace on the weird characters, making them into "206", then ran (desktop-read "/home/user/.emacs.d") again, and, viola, all my desktop files were properly loaded. So, thanks, thanks, thanks... I can get back to work now. I can say with certainty that the garbage characters (in the stead of "206") weren't due to the crash; my last ".emacs.desktop" saved was over a week ago, well before the crash. Secondly, I don't see how a system crash would change every instance of "206" interspersed throughout a file to "<81>". I think that's pretty much infunkingpossible to happen. Moreover, after all my desktop files were loaded, I ran "M-x desktop-save" and looked to the new .emacs.desktop file, and no more "<81>" characters. But emacs seems to be having sporadic problems correctly representing characters, so that's a possibility. Thanks again, John, for the suggestion.