all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: `make' written in elisp
Date: Tue, 04 Jan 2005 00:10:55 +0100	[thread overview]
Message-ID: <x5zmzqw1kw.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1ClXs5-0002EF-UO@neutrino.iwi.uni-sb.de> (Ralf Angeli's message of "Mon, 03 Jan 2005 20:28:05 +0100")

Ralf Angeli <angeli@iwi.uni-sb.de> writes:

> * Richard Stallman (2005-01-03) writes:
>
>>     At least it should be able to call things like `configure'
>>     which is a mandatory step in the build process of packages like
>>     AUCTeX and preview-latex.  During this step the values of some
>>     important variables are determined and written to the package's
>>     site configuration file.
>>
>> Why is it important for Emacs Lisp packages to do that sort of
>> thing?
>
> Automatically determining variables specific to the site the package
> is being installed at configuration time is a means to cut down load
> times.  There are things where it is not efficient or feasible to
> carry out the respective tests each time the package is loaded.
>
> As an example, in AUCTeX we are currently using `configure' to
> determine locations where TeX trees are located.  The resulting
> value is used at runtime for speeding up file searches.

I am not actually convinced that this is a good idea: I'd prefer it
that _if_ AUCTeX is made to match some package layout, then the whole
installation/configuration will be performed by Lisp.

Probably cached in customize variables, and with an option to redo the
detection on demand (in case you want to experiment with different
setups of TeX distributions or similar).

I'd really like it if we could skip all of the autoconf magic (which
is particularly painful and error-prone dealing with paths with spaces
and backslashes) for a reasonably easy Elisp solution.  It would
appear that with some of the mentioned functions in this thread, this
might be possible.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-01-03 23:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30 19:31 `make' written in elisp Michael Schierl
2003-12-31 22:57 ` Richard Stallman
2003-12-31 23:14   ` Michael Schierl
2004-01-01 21:10     ` Richard Stallman
2004-01-01 21:37       ` Michael Schierl
2004-01-04 23:25 ` Stefan Monnier
2005-01-02 16:06   ` Richard Stallman
2005-01-02 23:22     ` David Kastrup
2005-01-02 23:55       ` Ralf Angeli
2005-01-03  0:07         ` David Kastrup
2005-01-03  0:25           ` Ralf Angeli
2005-01-03  4:32             ` Richard Stallman
2005-01-03  8:02               ` David Kastrup
2005-01-03  9:36                 ` Eli Zaretskii
2005-01-03 16:45                   ` Stefan Monnier
2005-01-03  9:10               ` Ralf Angeli
2005-01-03 18:29                 ` Richard Stallman
2005-01-03 19:28                   ` Ralf Angeli
2005-01-03 23:10                     ` David Kastrup [this message]
2005-01-04  3:38                     ` Richard Stallman
2005-01-04 11:17                       ` Ralf Angeli
2005-01-03  0:26       ` Stefan
2005-01-03 11:05         ` Stephen J. Turnbull
2005-01-03 17:16           ` Stefan Monnier
2005-01-04 12:00             ` Stephen J. Turnbull
2005-01-04 13:59               ` Stefan
2005-01-04 14:07                 ` Miles Bader
2004-03-31 22:31 ` patch for locate-file-completion? Nic Ferrier
2004-04-01 17:34   ` Richard Stallman
     [not found] <E1CloEh-0004Sl-Hg@monty-python.gnu.org>
2005-01-04 16:10 ` `make' written in elisp Eric M. Ludlam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x5zmzqw1kw.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.