"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
David Kastrup writes:
> nobody with access to that tree at the current point of time
> would be interested into making the hallowed XEmacs
> infrastructure reproduce the binary package that AUCTeX builds.
A minor correction. I've tried, and so has Uwe, both without
success.
Well, I'd say the problem is that you are trying to modify the
existing decades-old AUCTeX packaging in your tree to match the new
requirements.
That's just a bunch of unnecessary work. Just cut out the history.
Let the AUCTeX Makefile build an XEmacs package tree (or a finished
binary package): this generates all the necessary startup files with
all the necessary relative paths. Then go backwards from the finished
binary package, dissecting it into your source tree arrangement.
All the files are there then. You just need to arrange them in your
source tree order before the scripts compiling and copying them are
run, and are finished.
I'm sure it can be done,
If it is not trivial once your start from the prebuilt XEmacs tree,
your build infrastructure is so deficient that it is not worth making
it mandatory.
but it's not high on my priority list. Since (aside from Uwe)
I've
still not seen any interest in contributing to an up-to-date binary
package, it's not likely to get increased priority soon.
Yup, what I said: XEmacs developers _will_ deny that anybody is
interested in AUCTeX.
It is not that I am not used to it: the usual reaction for bug reports
in central points of XEmacs is to deny that anybody is interested in
_XEmacs_ (thanks to the modularization of XEmacs, one can believe
central parts of it dead without wasting thought on the possibly
depressing idea that it might affect the whole) and that there is no
priority in fixing it since there are not many that still bother to
complain.
For all that I know, specifying binary format image file names in an
image descriptor is _still_ blowing up XEmacs 21.4 (and likely 21.5,
too) once dired gets loaded. This bug was reported at least 4 years
ago IIRC. Let me take a look:
1.5 (nixsf 19-Mar-02): ;; TODO: Generalize this so we can create the fixed
icons using it.
1.5 (nixsf 19-Mar-02):
1.38 (nixsf 16-Apr-02): ;; Argh, dired breaks :file :(
1.38 (nixsf 16-Apr-02): ;; This is a temporary kludge to get around that until
a fixed dired
1.38 (nixsf 16-Apr-02): ;; or a fixed XEmacs is released.
1.63 (dakas 09-Feb-05):
1.60 (dakas 18-Oct-04): (defun preview-create-icon-1 (file type ascent)
1.5 (nixsf 19-Mar-02): "Create an icon from FILE, image TYPE and
ASCENT."
1.55 (dakas 19-Jan-03): (let ((glyph
1.55 (dakas 19-Jan-03): (make-glyph
1.55 (dakas 19-Jan-03): (vector type
1.55 (dakas 19-Jan-03): :file file
1.55 (dakas 19-Jan-03): :data (with-temp-buffer
1.55 (dakas 19-Jan-03): (insert-file-contents-literally file)
1.55 (dakas 19-Jan-03): (buffer-string))))))
1.55 (dakas 19-Jan-03): (set-glyph-baseline glyph ascent)
1.55 (dakas 19-Jan-03): glyph))
See the additional kludge with :data? It was brought to attention
briefly to XEmacs development at that time (2002). I brought it up
several times afterwards with a few years distance in between.
Anyway, there seems to be little point in doing the whole Dead Parrot
Sketch _again_.
The problem I have with XEmacs is not that it is dead as a whole (no
developer feels any responsibility to fix things that are not strictly
in his module of personal interest). The problem I have is with the
cult of denial around it since it makes one waste so much time.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta