Re: Error report on startup

[Herbert Euler]

> I don't see anything confusing. You're manually loading some-file.el
> and reading its content in the context of loading .emacs, so certainly
> it is ~/.emacs which is not valid (or, which is doing something
> invalid). That the error comes from processing an elisp module is
> irrelevant. It's not different to loading a non-lispy data file in
> .emacs and then doing some kind of processing with it that causes an
> error.
>
> If instead you used `load' or `require' to load some-file.el you'd get:
>
>  An error has occurred while loading `c:/home/.emacs':
>
>  End of file during parsing: c:/emacs/site-lisp/some-file.el
>
>  To ensure normal operation, you should investigate and remove the
>  cause of the error in your initialization file.  Start Emacs with
>  the `--debug-init' option to view a complete error backtrace.

It is just an explain to the general case.  If you are loading a library,
which you are not familiar with and it does this, how could you
know which file is invalid?

For me, the library is type-break mode, and the file is ~/.type-break.
If I did not read the source and did some digging work, I cannot
know it is the file ~/.type-break that causes the error.

Regards,
Guanpeng Xu

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/