From: Peter Dyballa <Peter_Dyballa@Web.DE>
Subject: Re: emacs and desktop-read
Date: Thu, 28 Apr 2005 21:52:47 +0200 [thread overview]
Message-ID: <1b291aca6b086b424558df6923f46c83@Web.DE> (raw)
In-Reply-To: <d4r1fl$aqa$1@defalla.upc.es>
Am 28.04.2005 um 18:03 schrieb FCC:
> I create a .emacs.desktop file where the buffers are from a shared
> FAT32
> disk between WinXP and Debian. If I try to read this .emacs.desktop
> using (desktop-read), it fails:
> Desktop: 0 buffers restored, 3 failed to restore.
> If I exit emacs and restart it, then I get:
> Desktop: 1 buffer restored, 2 failed to restore.
> Any ideas as to what to do?
>
Read that file and notice the entries that are different from either
the Windows XP or the debian perspective. The cure: either delete those
(and make them never to appear again) or unify the view from both OS'
to the fat disk.
--
Greetings
Pete
next prev parent reply other threads:[~2005-04-28 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 16:03 emacs and desktop-read FCC
2005-04-28 19:52 ` Peter Dyballa [this message]
[not found] ` <mailman.3354.1114718066.2895.help-gnu-emacs@gnu.org>
2005-04-29 8:52 ` FCC
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=1b291aca6b086b424558df6923f46c83@Web.DE \
--to=peter_dyballa@web.de \
/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).