[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS HEAD fails to build on OSX 10.4 (macterm.c broken?)
From: |
Dan Nicolaescu |
Subject: |
Re: CVS HEAD fails to build on OSX 10.4 (macterm.c broken?) |
Date: |
Tue, 04 Sep 2007 14:29:55 -0700 |
Richard Stallman <address@hidden> writes:
> Of course not. But if the build does support the Carbon|w32|X11
interface,
> then it makes sense to preload (mac|w32|x)-win.el even if the user will
> occasionally run with -nw in which case the file will not be used.
>
> Why preload them if in some sessions they will not be used?
> Is the purpose just to speed up startup? If so, how much
> difference does it make?
I don't know if it supposed to speed startup, but I suppose it's
probably some other reason.
There's code in `command-line' that tries to make sure that the
WINDOW_SYSTEM-win file is loaded, and it errors out if it is not.
It then proceeds to call the x-handle-args (all the
term/*-win.el files provide such a function)
After that the function
WINDOW_SYSTEM-initialize-window-system. (all the term/*-win.el files
provide such a function now).
Again, this is just reading the code, not implying anything about why
any of these things are done in that way.
So what is the problem with having *-win loaded by default?
This discussion started because the port was having issues because
mac-win.el was requiring "url" for some of its functions. Those can be
moved to another file and the port can arrange to have the functions
in question properly loaded.