coding system oddity

Richard Zidlicky writes: This is not expected. It's not hard to imagine the code the leads to this result, but it's incorrect; we'll fix it. (I don't see a hurry, it may take some time. Patches welcome!) The undecided coding system is a sentinel, and should always be changed as the end result of autodetection, presumably to default-buffer-file-coding-system in the case This is a different bug (a user could set buffer-file-coding-system). In the case of buffer-file-coding-system(-for-write) being 'undecided or similar, the writer function (output might not be to a file) should error. And this is a third bug. I thought Aidan had fixed this, but I guess it's only for his new unibyte coding systems. If you don't mind explaining, how are you in this situation frequently enough to figure out what happened, let alone care? I don't think I've ever edited an existing file with zero-size. If there's a common workflow that leads to this, maybe there's more hurry than I thought. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta