[Bug: 21.5-b27] Suboptimal interaction of latin-unity and VM.

Fabrice Popineau Fabrice.Popineau at supelec.fr
Tue Feb 13 07:55:04 EST 2007


* Aidan Kehoe <kehoea at parhasard.net> writes:

    > $ xemacs-21.5-b27 -vanilla &

    > In *scratch*, I type:

    > (latin-unity-install) C-j => (latin-unity-sanity-check)

    > (setq font-running-xemacs t) ;; to work around an issue W3 is
    > seeing => t

    > 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.”

    > This time it lists:

    >     iso-8859-1 iso-8859-2 iso-8859-3 iso-8859-4 iso-8859-9
    > iso-8859-15 utf-8 iso-2022-7 ctext escape-quoted

    > as recommended because they can encode any character in the
    > buffer. The folder in question is available at
    > http://www.parhasard.net/spam.bz2 .

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.

Thanks for any clue,

Fabrice




More information about the XEmacs-Beta mailing list