David Kastrup <[EMAIL PROTECTED]> writes: > As far as I can see, it sets the complete buffer coding system, not > just the base buffer coding system. That would basically mean that > a possibly detected line ending convention would get replaced with > some default.
Maybe. latexenc-find-file-coding-system only returns the base coding system (that is without line ending information). At least on my system emacs still detects the correct line ending information in addition to the coding system detected by latexenc-find-file-coding-system. Christian actually found a bug in a Makefile when compiling under MingW. And his fix made the problem disappear. Christian, I hope you don't mind me quoting your e-mail here: > There is a problem with the Makefile for the lisp subdirectory when it is > executed within a MingW environment. make's internal variable $(CURDIR) > expands to /d/emacs/src/lisp. When generating loaddefs.el emacs then tries > to write the file d:/d/emacs/src/lisp/loaddefs.el, which fails. > > Hence, loaddefs.el does not get updated. So > latexenc-find-file-coding-system is undefined at runtime which explains the > behaviour I've encountered. > > I patched lisp/makefile.w32-in so that the path to loaddefs.el is ommitted. > Since emacs gets called from within the lisp directory to create the > autoloads, loaddefs.el is still created in the correct location. Kind regards, -- Arne Jørgensen <http://arnested.dk/> _______________________________________________ bug-auctex mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-auctex
