Re: dired and {coding-systems|MULE} together breaks `make-glyph'.

nix> Alas, if the filename of the glyph being instantiated matches a handler nix> in the file-name-handler-alist, that handler gets invoked to do the nix> work, but the operation passed to the handler is 'insert-file-contents, nix> not 'insert-file-contents-literally --- so when the handler goes off and nix> reinvokes the operation on the remote site, it uses the wrong function nix> call, and takes coding-systems into account even though glyph-loading I don't think `insert-file-contents' is the wrong function, because there's nothing inherent about it that takes coding systems into account (`insert-file-contents-literally' *calls* `insert-file-contents' eventually). Rather, it dynamically binds the various implicit parameters determining the coding system. (Or do they?) I think you're saying these get rebound during the process, but I'm not sure. If so, we need to figure out where. Dired sure isn't doing it. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla