From: ken <gebser@mousecar.com>
To: Juanma Barranquero <lekktu@gmail.com>,
GNU Emacs List <help-gnu-emacs@gnu.org>
Subject: Re: problem reading ~/.emacs.desktop
Date: Sun, 20 Sep 2009 05:26:41 -0400 [thread overview]
Message-ID: <4AB5F551.5010909@mousecar.com> (raw)
In-Reply-To: <f7ccd24b0909192029m64e2103s5840d10e68ce970a@mail.gmail.com>
On 09/19/2009 11:29 PM Juanma Barranquero wrote:
> On Sun, Sep 20, 2009 at 05:04, ken <gebser@mousecar.com> wrote:
>
>> Very cool idea. ....
I like the idea of creating, in effect, a new and totally clean
environment in which to test. Another step in the process to implement:
before setting the new $HOME variable, run "bash -" (or whatever shell
used). This creates a new shell. The new shell's environment, though a
copy of the previous, can be manipulated and changed and after testing
easily wiped out simply by exiting that new shell.
>
>> ....
>
> Yeah, my mistake, I meant desktop-read.
Small thing. Funny how the mind can lose one little piece in a long
series of steps. We were already by then on the same page, so no big deal.
>
> This test shows that your Emacs setup does not have any trouble
> reading or writing desktop files. So the one that gives you trouble
> must have some formatting problem or somesuch. I'd suggest just
> deleting it and recreating it (by loading the files you want to have
> and then M-x desktop-save'ing).
In fact that's pretty much what I did. I grepped the old
".emacs.desktop" to output just the filenames and fed this into emacs at
load time. I knew emacs would load all the files, but I didn't think it
would remember the point (text cursor) position was in my previous
session. Somehow it did though... that's a puzzle to me.
That was my plan of last resort-- at least I would have the files loaded
that I wanted. My other concern though was for other folks who upgrade
emacs and would expect it to load up all their files from their last
pre-upgrade session; this wouldn't happen for them. That is,
.emacs.desktop has (I think) a version number; it should recognize it
and take appropriate action and provide a smoother upgrade path. This
would include an accounting for a simultaneous system upgrade from some
other locale definitions to UTF-8; this might have been (part of?) the
problem with "205" displaying as an 'I' with a diacritical mark. I'm
not sure... just a hunch.
>
>> Hey, you're good. Yeah, I've got some of that in one of my files. But
>> what's the "suffix" that's missing?
>
> It means that Emacs thinks that the Local Variables section has a
> format problem; that's why I ask about CRLF vs LF.
>
> ....
Thanks for the explanation... very good and very clear. With that I'll
search through my files for Local Variables and should be able to locate
and fix what needs it.
Juanma, thanks for all the tips, help, and clarifications. You're on my
A-Team list.
Best,
ken
prev parent reply other threads:[~2009-09-20 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 22:57 error on start-up: font not defined ken
2009-09-15 3:09 ` problem reading ~/.emacs.desktop [was: Re: error on start-up: font not defined] ken
2009-09-15 9:24 ` problem reading ~/.emacs.desktop ken
2009-09-15 9:37 ` Juanma Barranquero
2009-09-16 8:14 ` ken
2009-09-16 8:30 ` Juanma Barranquero
2009-09-16 8:39 ` Juanma Barranquero
2009-09-20 3:04 ` ken
2009-09-20 3:29 ` Juanma Barranquero
2009-09-20 9:26 ` ken [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AB5F551.5010909@mousecar.com \
--to=gebser@mousecar.com \
--cc=help-gnu-emacs@gnu.org \
--cc=lekktu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).