David Kastrup <[email protected]> writes: >>> At any rate: while there was a wagonload of work invested in that >>> area, it would appear that some of that meets the label "too >>> clever". >> >> Seems so, especially wrt the single-user install. AUCTeX is the only >> elisp package I know that you can't just unpack/clone, optionally >> configure & make and then add that directory to load-path and be done. > > Huh? How are any other package's info files going to end up compiled > and placed within the Emacs info tree?
Ok, ok, you also need to add the package's doc dir to Info-directory-list, and possibly generate a dir file in there with install-info. >> Nevertheless, it works fine for me, and is less hassle than the >> documented way. I wonder if it would make sense to document that >> instead of the current advice for user-installs in the docs. > > No. It never makes sense in the long run to document how to work > around the design of software. > > If you ever feel the urge to do that, resist it. Change the design > instead. It's doing just fine with normal system installs, building XEmacs packages and what not. But therefore it's complicated. I'm not brave enough to put my hands on it. Bye, Tassilo _______________________________________________ auctex mailing list [email protected] https://lists.gnu.org/mailman/listinfo/auctex
