Fabrice Popineau wrote:
* Aidan Kehoe <kehoea(a)parhasard.net> writes:
> I type M-x vm-visit-folder RET /tmp/aidan/spam RET
> I make a change, press S , and I get the coding system conflict
> message. It says, again, that:
> “All preapproved coding systems (buffer-default==binary
> preferred==utf-16-little-endian-bom) fail to appropriately encode
> some of the characters present in the buffer.”
Has this issue been solved ? I have upgraded my xemacs to the latest
21.5 cvs sources and xemacs-packages and I seem to get a similar
problem. I can't even byte-compile a .el file, because I get this very
same message about the compile log buffer.
Hi Fabrice, hope you're doing well. :-)
When I encountered this problem last week, I could restore the old
behavior with the patch
--- DEL.latin-unity.el 2006-08-14 09:52:34.000000000 +0200
+++ latin-unity.el 2007-02-06 23:25:41.000000000 +0100
@@ -484,7 +484,7 @@
;; #### actually we can do the whole charset here
;; precompute and set a property on the cs symbol
(setq skipchars (concat skipchars (list ch)))
- (when (= flag 0) (setq lsets (logior
latin-unity-non-latin-bit-flag lsets)))
+ ;(when (= flag 0) (setq lsets (logior
latin-unity-non-latin-bit-flag lsets)))
(setq lsets (logior flag lsets)))))
;; The characters skipped here can't change asciisets
(skip-chars-forward skipchars))))
Though Stephen will probably tell you that this is the wrong
solution, as it restores another bug. Nevertheless, since I never
encountered the other bug, but have this one regularly, I use this
patch until Stephen comes up with a better solution. Maybe that
works for you as well.
Best,
Joachim
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: jschrod(a)acm.org
Roedermark, Germany
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta