Brian C. White writes ("Re: Emacs per-package startup files"):
...
> [someone:]
> > So, do these files go in /var/lib/emacs, /etc/emacs, or
> > /usr/lib/emacs/site-lisp, and why? I can set it up and send changes
> > to the emacs package maintainers this week
> Hmm. As for dpkg needing install-elisp, I'm not quite sure I buy that,
> because it would seem to argue that *any* install-* should be included
> in dpkg. Then again, there is only install-info which *is* in dpkg,
> and install-mime which is in mime-support which has it's own
> justification. The
Mark Eichin writes ("Re: Emacs per-package startup files"):
...
> [it would make it easier to fix the
> /etc/passwd problem that mhpower mentioned], but in those cases we
> can't really change the "database" because of existing use, whereas
> with emacs we a
[EMAIL PROTECTED] writes ("Re: Emacs per-package startup files"):
> Umm, /usr/lib/emacs/site-lisp/ is already there, and already the right
> place for this sort of thing. Next question?
Err, I don't think so. Files in /usr/lib/emacs/site-lisp aren't
loaded automatically
> "EB" == Erick Branderhorst <[EMAIL PROTECTED]> wrote:
EB> How will these files be read. In alphabetical or fileposition order?
EB> Some scripts written in these might work only properly if some other
EB> script is executed first. I can't come up with some proper example
EB> but I can imag
> "EB" == Erick Branderhorst <[EMAIL PROTECTED]> wrote:
EB> How will these files be read. In alphabetical or fileposition order?
EB> Some scripts written in these might work only properly if some other
EB> script is executed first. I can't come up with some proper example
EB> but I can imag
> "IJ" == Ian Jackson <[EMAIL PROTECTED]> wrote:
IJ> /etc/emacs/site-start.d ?
There would be something else inside /etc/emacs or just site-start.d?
If not, it seems we need a better name.
/etc/site-start.d?
/etc/emacs.d?
/etc/emacs-start.d?
/etc/emacs-lisp.d?
Yes, I know would nice to have
Erick Branderhorst writes:
>
> > If the files there really depend on each other, then it may be nice
> > to require that each .el file contains
> >
> >(provide 'site-start-xxx)
> >
> > (as the *last* line so nothing is provided in case of error), and other
> > files will just us
> If the files there really depend on each other, then it may be nice
> to require that each .el file contains
>
> (provide 'site-start-xxx)
>
> (as the *last* line so nothing is provided in case of error), and other
> files will just use
>
> (require 'site-start-xxx)
>
> as ne
Erick Branderhorst writes:
>
> > OK, so we've decided to have packages put their Emacs startup stuff in
> > a directory, with one file per package.
> >
> > The directory obviously ought to go in /etc, and the files made
> > conffiles, so that the sysadmin can reconfigure things.
> >
> >
> OK, so we've decided to have packages put their Emacs startup stuff in
> a directory, with one file per package.
>
> The directory obviously ought to go in /etc, and the files made
> conffiles, so that the sysadmin can reconfigure things.
>
> /etc/emacs/site-start.d ?
Please wait a minute.
H
OK, so we've decided to have packages put their Emacs startup stuff in
a directory, with one file per package.
The directory obviously ought to go in /etc, and the files made
conffiles, so that the sysadmin can reconfigure things.
/etc/emacs/site-start.d ?
Ian.
12 matches
Mail list logo
