Date: Mon, 26 Jun 1995 15:22:54 +0200 (MSZ) From: me@tartufo.pcs.dec.com (Michael Elbel) To: asami@cs.berkeley.edu (Satoshi Asami) Cc: me@freebsd.org, jmz@cabri.obs-besancon.fr, ports@freebsd.org Subject: Re: xemacs port in combination with ispell port Message-ID: <m0sQE7r-000PZoC@tartufo.pcs.dec.com> In-Reply-To: <199506261018.DAA11505@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Jun 26, 95 03:18:35 am
next in thread | previous in thread | raw e-mail | index | archive | help
> * >$ ls -l /usr/local/lib/emacs/site-lisp/ > > * This won't help with xemacs, however, since xemacs has its own > * lisp directory /usr/local/lib/xemacs/site-lisp/ :-( > > And emacs' site-lisp directory has just moved into /usr/local/share > with the upgrade to 19.29. :< > > * It might be that there should be a directory under /usr/local/lib > * for common special lisp stuff. > > Agreed. Someone want to go into all the emacs-based editor ports (and > ispell and such, hmm do any tex ports come with .el files?) to let > them all agree on one location, say, /usr/local/share/emacs/site-lisp? > (That's where emacs is now, and others should follow, I reckon.) > If I'm not severely mistaken this won't work so easily. There might be site-lisp code that is dependent on the editor being used - I.e. settings for special xemacs or fsfmacs features. I agree that it's not *very* probable that both xemacs and fsfmacs are insalled on the same machine, but one never knows and would have to ensure that at least no files get overwritten with versions from another type of editor. Michael -- Michael Elbel, PCS GmbH, Muenchen, Germany - me@FreeBSD.org Fermentation fault (coors dumped)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0sQE7r-000PZoC>