Re: [Bug: 21.5-b29] babel does not work, encoding problem
Samuel Bronson writes:
It would be useful if there was a way to ask "what coding
systems were
used for that process that just ran",
There is. `process-coding-system'. Of course you have to keep a
handle to the process around to access, which probably a lot of simple
usages don't. Emacs LISP encourages that kind of sloppy programming,
unfortunately.
or some other way of finding out what is decided without having to
do elisp debugging/tracing. It would be even better if this would
also explain how it was decided, step-by-step. Some kind of
toggleable tracing, maybe?
Feel free. But this is going to be hard because it's buried deep in
the lstream code. It should be possible to get that information out
of there, but you can't call LISP there, so it's a bit annoying.
Unfortunately, Emacs LISP is a pretty sucky language in this respect.
In theory, codecs could be coded in LISP, but at least the times I've
tried this it was too slow. Also, of course we need to read in the
LISP before the LISP environment is properly initialized (eg, when
building XEmacs). So unlike Python, all of our codecs are done in
languages other than LISP (C or CCL which is an assembler-level little
language for writing codecs).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta