As I complained various times, x-symbol has a problem with large
files. I am not entirely sure, whether it has to do with the
use of lazy-shot or lazy-lock or ... Or with the way x-symbol
has implemented the x-symbol-write-file-hook.
Anyhow x-symbols sometimes freezes the whole xemacs and the result is a
not correctly encoded file, and in the case of Mule, a badly damaged
Now I thought that it might help if in the case of a huge file, I narrow
to a certain region and do the edit there. Of course x-symbol still has
to save the whole buffer but may be fortification is more efficient if
the buffer is narrowed?
Can anybody comment on this?
XEmacs-Beta mailing list