[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug using tramp in Emacs 22.1.1
From: |
Adam Jenkins |
Subject: |
Re: Bug using tramp in Emacs 22.1.1 |
Date: |
Wed, 23 Jul 2008 14:16:30 -0500 |
Thanks,
In a clean environment using the emacs -Q I'm getting this when I try
to open a file.
Debugger entered--Lisp error: (error "unknown file I/O primitive:
make-auto-save-file-name")
signal(error ("unknown file I/O primitive: make-auto-save-file-name"))
error("unknown file I/O primitive: %s" make-auto-save-file-name)
tramp-file-name-for-operation(make-auto-save-file-name)
apply(tramp-file-name-for-operation make-auto-save-file-name nil)
tramp-file-name-handler(make-auto-save-file-name)
ad-Orig-make-auto-save-file-name()
(setq ad-return-value (ad-Orig-make-auto-save-file-name))
(if (and (buffer-file-name) (tramp-tramp-file-p ...)
tramp-auto-save-directory) (setq ad-return-value
(tramp-make-auto-save-file-name ...)) (setq ad-return-value
(ad-Orig-make-auto-save-file-name)))
(let (ad-return-value) (if (and ... ... tramp-auto-save-directory)
(setq ad-return-value ...) (setq ad-return-value ...))
ad-return-value)
make-auto-save-file-name()
after-find-file(nil t)
find-file-noselect-1(#<buffer .bashrc>
"/ssh:address@hidden:/home/cezar/.bashrc" nil nil
"/ssh:address@hidden:/home/cezar/.bashrc" ((52 . 47110) (-1 0)))
find-file-noselect("/ssh:address@hidden:/home/cezar/.bashrc" nil nil nil)
find-file("/ssh:address@hidden:/home/cezar/.bashrc")
dired-advertised-find-file()
call-interactively(dired-advertised-find-file)
Then on second attempt I get this
Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p (35148))
time-subtract((18493 35148) (18493 (35148)))
tramp-time-diff((18493 35148) (18493 (35148)))
tramp-handle-verify-visited-file-modtime(#<buffer .bashrc>)
apply(tramp-handle-verify-visited-file-modtime #<buffer .bashrc>)
tramp-sh-file-name-handler(verify-visited-file-modtime #<buffer .bashrc>)
apply(tramp-sh-file-name-handler verify-visited-file-modtime
#<buffer .bashrc>)
tramp-file-name-handler(verify-visited-file-modtime #<buffer .bashrc>)
verify-visited-file-modtime(#<buffer .bashrc>)
find-file-noselect("/ssh:address@hidden:/home/cezar/.bashrc" nil nil t)
find-file("/ssh:address@hidden:/home/cezar/.bashrc" t)
call-interactively(find-file)
recursive-edit()
byte code that I can't copy paste for some reason
debug(error (error "unknown file I/O primitive: make-auto-save-file-name"))
signal(error ("unknown file I/O primitive: make-auto-save-file-name"))
error("unknown file I/O primitive: %s" make-auto-save-file-name)
tramp-file-name-for-operation(make-auto-save-file-name)
apply(tramp-file-name-for-operation make-auto-save-file-name nil)
tramp-file-name-handler(make-auto-save-file-name)
ad-Orig-make-auto-save-file-name()
(setq ad-return-value (ad-Orig-make-auto-save-file-name))
(if (and (buffer-file-name) (tramp-tramp-file-p ...)
tramp-auto-save-directory) (setq ad-return-value
(tramp-make-auto-save-file-name ...)) (setq ad-return-value
(ad-Orig-make-auto-save-file-name)))
(let (ad-return-value) (if (and ... ... tramp-auto-save-directory)
(setq ad-return-value ...) (setq ad-return-value ...))
ad-return-value)
make-auto-save-file-name()
after-find-file(nil t)
find-file-noselect-1(#<killed buffer>
"/ssh:address@hidden:/home/cezar/.bashrc" nil nil
"/ssh:address@hidden:/home/cezar/.bashrc" ((52 . 47110) (-1 0)))
find-file-noselect("/ssh:address@hidden:/home/cezar/.bashrc" nil nil nil)
find-file("/ssh:address@hidden:/home/cezar/.bashrc")
dired-advertised-find-file()
call-interactively(dired-advertised-find-file)
On Wed, Jul 23, 2008 at 1:44 PM, Michael Albinus <address@hidden> wrote:
> "Adam Jenkins" <address@hidden> writes:
>
>> I'm able to open a file, but I get the following error in the messages
>> buffer when ever I attempt to type in the buffer with the remote file.
>>
>> tramp-time-diff: Wrong type argument: number-or-marker-p, (23679)
>
> Strange, I don't remember such a problem. Could you, please, call
> "emacs -Q" in order to have a clean environment? Another useful
> information can be retrieved, if you enable [Options] -> [Enter Debugger
> on Error], before you run the test. The resulting backtrace should be
> helpful.
>
> Best regards, Michael.
>