Re: Auto save error
David (davidbe@goliat.upc.es)
Fri, 16 Dec 94 22:12:34 +0100
Hi again,
>>>>> On Thu, 1 Dec 94 15:28:11 +0100,
davidbe@goliat.upc.es (David) said:
>> 2. I start Dired 7.7. Suddenly I get autosave errors for regular
>> files (i.e. buffers associated with filenames), but it autosaves
>> mail buffers all right.
>> I have not issued one single command in this dired, and
>> auto-save.el (which struck me as a file that could have effect on
>> this behaviour) is not loaded. Any hints?
Sandy> Try loading auto-save.el. You'll gain some extra
Sandy> functionality, and _maybe_ your problem will go away ;-)
I have done that, but nope, I still get autosave error. Not for all
files though, e.g. my .newsrc was autosaved without problems today,
but my INBOX beeps at me every time.
Sandy> If you really don't like auto-save.el, try setting
Sandy> debug-on-error to t to generate a traceback, and send it to me.
I think I would like auto-save.el if it worked... As I have said
before, debug-on-error does not give a traceback for this error.
What this depends on is a mystery to me. If you hint me about an
entry point, perhaps I could do debug-on-entry?
Sandy> I think that I know the problem. All versions of Emacs 19
Sandy> prior to (and including 19.22) had a serious bug in the
Sandy> file-name-handler support, which both dired and efs use
Sandy> heavily. This bug was actually rather hard to fix. It was
Sandy> fixed in Emacs 19.23. I have added the package fn-handler.el
Sandy> as a backward-compatibility hack to try to use lisp overloads
Sandy> to fix up older versions of Emacs.
So why doesn't it work? Is there something wrong with fn-handler.el?
Something that is only affected when I run dired?
Sandy> If you are able to upgrade your Emacs, that should solve the
Sandy> problem.
This site had Emacs 18.54 as its official Emacs up till October, when
they considered the installation of 19.22 to be stable enough. I will
not be able to upgrade, but I change sites in February.
Sandy> Also, I will have a look to see if I can see where
Sandy> fn-handler.el is losing. A traceback will help here.
Again, give me hints on entry points, because debug-on-error does not
help.
Sandy> The reason why I also suggest using auto-save.el is that its
Sandy> auto-save support is in lisp. Because fn-handler.el is also in
Sandy> lisp, any of its overloads will not affect calls to primitives
Sandy> in the C code. Hence the builtin auto-save support is probably
Sandy> calling buggy file-name-handler code.
But where does dired.el come into this? I don't have any problems
before I run dired, so it must be something there.
/David
-------------------------------------------------------------------
David, datorligist davidbe@goliat.upc.es or cl2david@cling.gu.se
Ask for PGP public key, or check http://www.cling.gu.se/~cl2david
Do good --- be good --- feel good. Hakuna matata!