help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problem reading ~/.emacs.desktop


From: Juanma Barranquero
Subject: Re: problem reading ~/.emacs.desktop
Date: Wed, 16 Sep 2009 10:30:11 +0200

On Wed, Sep 16, 2009 at 10:14, ken <address@hidden> wrote:

> In the newly created ".emacs.desktop" file (created by the upgraded
> version of emacs), this same argument is displayed as an 'I' with a
> diacritical mark over it-- the same as the old one was in the Debugger.
>  (?)  The value of that character (as determined by "C-x =") is 205.

?? With Emacs 23.1, the version should be 206.

I'd like to know what happens when you do the following

  - create an empty directory and cd to it
  - set HOME to that directory
  - create a test file (let's call it test.txt) with a couple lines
  - then
       emacs -Q test.txt
       M-x desktop-save <RET>

> So then I edited ".emacs.desktop" to replace the 'I' with the
> diacritical mark with "205" (without the quotes).  And I comment out the
> code in ~/.emacs which invokes "desktop-read" and "desktop-save" and
> reload emacs and run these by hand.  I find that emacs has changed "205"
> to "206".  And though the files are read into emacs fine, I get this
> different error from Debugger:
>
> Debugger entered--Lisp error: (error "Local variables entry is missing
> the suffix")
>  signal(error ("Local variables entry is missing the suffix"))
>  error("Local variables entry is missing the suffix")
>  hack-local-variables()
>  normal-mode(t)
>  after-find-file(nil t)
>  find-file-noselect-1(#<buffer g-mob> "~/pub/g-mob" nil nil
> "~/pub/g-mob" (38245125 64771))
>  find-file-noselect("/home/zl/pub/g-mob")
>  desktop-restore-file-buffer("/home/zl/pub/g-mob" "g-mob" nil)
>  #[nil "       A
>
> This error isn't clear enough for me to figure out.  And it's probably
> over the head of most, if not all, of the people on this list.  But if
> anyone has a cogent guess as to how to fix this, I'd be willing to give
> it a try.
>
> Thanks again, Juanma, for your help.  It got me a little further toward
> resolution.
>
>
>
>



-- 
    Juanma




reply via email to

[Prev in Thread] Current Thread [Next in Thread]