From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Emacs Devel <emacs-devel@gnu.org>,
Michael Albinus <michael.albinus@gmx.de>
Subject: Re: Strange loading of vc-bzr with additional file-handler
Date: Sat, 19 Jul 2008 16:14:49 +0200 [thread overview]
Message-ID: <4881F6D9.10908@gmail.com> (raw)
In-Reply-To: <4881F1DC.2040404@gmail.com>
Lennart Borgman (gmail) wrote:
> Lennart Borgman (gmail) wrote:
>>> Here is more info. When trying to exit Emacs after the above error I
>>> got another error
>>>
>>> Debugger entered--Lisp error: (invalid-read-syntax "#")
>>> load("c:/emacs/p/080718/emacs/lisp/emacs-lisp/warnings.elc" nil t t
>>> nil)
>>> apply(load ("c:/emacs/p/080718/emacs/lisp/emacs-lisp/warnings.elc"
>>> nil t t))
>>> (let ((inhibit-file-name-handlers ...) (inhibit-file-name-operation
>>> operation)) (apply operation args))
>>> (if done nil (let (... ...) (apply operation args)))
>>> (unless done (let (... ...) (apply operation args)))
>>> (let ((done nil) ftype) (when (eq operation ...) (when ... ...)
>>> (unless ... ... ...)) (unless done (let ... ...)))
>>> sex-file-handler(load
>>> "c:/emacs/p/080718/emacs/lisp/emacs-lisp/warnings.elc" nil t t)
>>> warn("recentf mode: %s" "Symbol's function definition is void:
>>> vc-bzr-state-heuristic")
>>> byte-code(" \b!\" " [error warn "recentf mode: %s"
>>> error-message-string] 4)
>>> recentf-save-list()
>>> run-hooks(kill-emacs-hook)
>>> kill-emacs()
>>> save-buffers-kill-emacs()
>>> save-buffers-kill-terminal(nil)
>>> call-interactively(save-buffers-kill-terminal nil nil)
>>>
>>> This comes when executing code similar to that in
>>>
>>> (info "(elisp) Magic File Names")
>>
>> Some more errors, now after restarting
>>
>> apply: End of file during parsing:
>> c:/emacs/p/080718/emacs/lisp/url/url-handlers.elc
>> completion--some: End of file during parsing:
>> c:/emacs/p/080718/emacs/lisp/net/trampver.elc
>> apply: End of file during parsing:
>> c:/emacs/p/080718/emacs/lisp/dired.elc
>
> Sorry for sending this in small pieces, but here is where I believe the
> error is. Just before the code mentioned above I have put a call to
>
> (message "operation=%s, args=%s" operation args)
>
> Before the error I get
>
> operation=expand-file-name,
> args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc nil)
> apply: End of file during parsing:
> c:/emacs/p/080718/emacs/lisp/image-mode.elc
>
> So I guess there is an error in expand-file-name. Could tramp be
> involved (since there are special problems with the w32 file names)?
Since this looks very strang I give some more output here. After it have
gone through load-path and found image-mode.elc and calls load it goes
back to the first entry in load path (which is the directory where I
have predictive) and tries to expand the file name again against that
entry. Why?
And then there are several expand-file-name against nil with the found
file. Only the last one fails. Why?
operation=expand-file-name,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc nil)
operation=file-readable-p,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc)
operation=expand-file-name,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc nil)
operation=expand-file-name,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc
c:/EmacsW32/nxml/nxhtml/doc/img/)
operation=file-directory-p,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc)
operation=expand-file-name,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc
c:/EmacsW32/nxml/nxhtml/doc/img/)
operation=load, args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc nil t
t)
operation=substitute-in-file-name,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc)
operation=expand-file-name,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc
c:/dl/emacs/predictive/html/)
operation=expand-file-name,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc nil)
operation=file-readable-p,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc)
operation=expand-file-name,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc nil)
operation=expand-file-name,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc
c:/EmacsW32/nxml/nxhtml/doc/img/)
operation=file-directory-p,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc)
operation=expand-file-name,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc
c:/EmacsW32/nxml/nxhtml/doc/img/)
operation=file-truename,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc)
operation=expand-file-name,
args=(c:/emacs/p/080718/emacs/lisp/image-mode.elc nil)
apply: End of file during parsing:
c:/emacs/p/080718/emacs/lisp/image-mode.elc
next prev parent reply other threads:[~2008-07-19 14:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 13:30 Strange loading of vc-bzr with additional file-handler Lennart Borgman (gmail)
2008-07-19 13:41 ` Lennart Borgman (gmail)
2008-07-19 13:46 ` Lennart Borgman (gmail)
2008-07-19 13:53 ` Lennart Borgman (gmail)
2008-07-19 14:14 ` Lennart Borgman (gmail) [this message]
2008-07-19 15:49 ` Jason Rumney
2008-07-19 16:28 ` Lennart Borgman (gmail)
2008-07-19 16:42 ` Lennart Borgman (gmail)
2008-07-19 16:45 ` Johan Bockgård
2008-07-19 16:50 ` Lennart Borgman (gmail)
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=4881F6D9.10908@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).