auctex-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[AUCTeX-devel] Re: preview-latex 0.9.1 and AUCTeX 11.whatever


From: Jan-Åke Larsson
Subject: [AUCTeX-devel] Re: preview-latex 0.9.1 and AUCTeX 11.whatever
Date: Thu, 31 Mar 2005 09:21:55 +0200
User-agent: Mozilla/5.0 (X11; U; SunOS sun4u; sv-SE; rv:1.7.5) Gecko/20041222

David Kastrup wrote:
I think it would be better to create another aclocal.m4 macro that does this job in a more general way, something like AUCTEX_PATH_PREFIX(prefix1, prefix2, executable) which then sets the
prefix1 and prefix2 variables to the path-relative stuff in the
manner I outlined previously.

I have checked in a different proposal, which sets $emacsprefix. I
thought about it and I think it is better this way since we have
possibly different prefixes for emacs and tex,...

I have not implemented the explicit list of locations. The current code
matches ${emacsprefix}/.*/site-lisp which perhaps is good enough. I have
little experience with people modifying the beginning of load-path, is
this common? By the way, is there a reason for checking site-packages in
that AC macro, it is only called for GNU Emacs anyway?

Anyway, I have looked at the other things in aclocal.m4 and there are a
few things I do not like, most notably the relative directories. IMO it
would be better to use the absolute path ${lispdir}/preview than this
relative stuff. We'd get confusing (-ed) questions about this in
auctex-bugs I think.

Another question is if there really is a need for the complicated
TeX-tree path checking which doesn't work here anyway (...reading...)
Oh, I see. Here is the use for our different prefixes. Hmmm. I'll solve
this too, given some time. The easy way is of course to do
AC_PREFIX_PROGRAM(tex)...no, that won't work. This architecture-specific
path component won't get stripped. Bah. I'll figure something out.

/JÅ




reply via email to

[Prev in Thread] Current Thread [Next in Thread]