On Fri, 1 May 1998, Ionut Borcoman at debian wrote: > Hi, > > Thanks to all for the quick answer. The > > $ emacs -batch -q -no-site-file -f batch-byte-compile <source-file(s)> > > is what I've wanted. But this leads me to another question: now, as a 'system > adminstrator" of my own PC, I just wonder which is the right way to add files > to emacs and to make them available to those who are working on my computer. > For instance, I want to add the JDE and don't know exactly were to put it and > how to make it system available. > > Some advices would be welcome, especially as I'm a newbye in Emacs, Linux, > etc... >
I'm not sure there is a "right" answer to this, but my recommendation would be to put this stuff in /usr/local/... Using /usr/local in this way makes it very clear [at least to me :)] what is "manually" built and installed from what is installed the Debian way using either dselect or dpkg. I add all of the locally added stuff to emacs by creating a /usr/local/share/emacs into which I add subdirectories for each "component". I forget why I put it in /usr/local/share, the Debian distribution puts all of the emacs LISP in /usr/lib/emacs/..., but it must of made sense to me at one point. You can really put it anywhere you like as long as the emacs load-path is updated but somewhere in /usr/local is the conventional place to put locally added/updated stuff. So, specifically, to install the JDE stuff I would do something like adding a directory: /usr/local/share/emacs/jde-2.0 into which I would install the JDE files. Then, in your .emacs file you must do something like: (setq load-path (nconc '("/usr/local/share/emacs/jde-2.0") load-path)) to add this locally installed addition to the load-path so emacs can find it. There should be some installation notes with these additional emacs components that specify exactly what you must do in .emacs to make it available. Hope this helps... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]