[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: autosaving isn't working.
From: |
Ryan Hodges |
Subject: |
Re: autosaving isn't working. |
Date: |
12 Aug 2003 10:33:16 -0700 |
On Tue, 2003-08-12 at 04:22, Kai Großjohann wrote:
> Ryan Hodges <address@hidden> writes:
>
> > For some reason autosaving doesn't work with tramp. As soon as the
> > autosave mechanism is triggered, the following message is printed:
> >
> > Auto-saving...
> > Auto-saving cc_publication_manifest.pm: Opening output file: no such
> > file or directory,
> > /usr/src/build/225504-i386/BUILD/emacs-21.2/src/#cc_publication_manifest.pm#
>
> This looks like a local file.
>
> Do you have problems with autosaving all files, or just remote files?
>
auto save only fails with remote files.
> What does M-: (make-auto-save-file-name) RET print when you invoke it
> from a buffer where autosaving fails?
>
When tramp-auto-save-directory is set to nil, the above evaluates to:
the /usr/src/build.... pathname.
However, if tramp-auto-save-directory is set to a pathname, then the
above evaluates to what its supposed to evaluate to.
Hopefully, that should enable you to reproduce the problem. I did a
search on google for the error message. It happened to one other guy
who said the problem just kind of disappeared on its own.
Ryan
> > Auto-saving...done
> > Auto-saving...
> > Auto-saving cc_publication_manifest.pm: Opening output file: no such
> > file or directory,
> > /usr/src/build/225504-i386/BUILD/emacs-21.2/src/#cc_publication_manifest.pm#
> >
> > Here is some debugging information:
> >
> > Emacs : GNU Emacs 21.2.1 (i386-redhat-linux-gnu, X toolkit, Xaw3d
> > scroll bars)
> > of 2003-02-19 on porky.devel.redhat.com
> > Package: tramp (2.0.36)
> >
> > My tramp autosave directory is set to nil.
>
> It might also help to set it to a directory name. For example, I
> created a directory ~/.tramp and then (setq tramp-auto-save-directory
> "~/.tramp/").
>
> But maybe you *want* the autosaves to go to the remote directory, in
> that case, I'll have to fix the bug I'm afraid :-)