Re: [Failure] XEmacs 21.5-b29 "garbanzo" 8905163c49c5+ configured for `i686-pc-linux'. (was: [COMMIT] #'find-file: set b-f-c-s even on error (cf. non-existent files), )
Aidan Kehoe <[email protected]>
| Newsgroups | gmane.emacs.xemacs.build-reports,gmane.spam.detected |
|---|---|
| Message-ID | <[email protected]> |
Ar an ceathrú lá déag de mí Iúil, scríobh Mats Lidell: > >>>>> Aidan Kehoe <[email protected]> writes: > > Aidan> Mats, this will resolve the issues you’re seeing (apart from > Aidan> the query-coding test failures; I’m wondering what to do about > Aidan> them myself.) > > So this below is consistent with what you get now? Yes. In query-coding-tests.el, I’m checking for ASCII-transparency in query-coding-region for all the coding systems that are ASCII-transparent in their encoding (from a trivial check). For coding systems of the iso2022 type (in this case, that are created in the latin-euro-standards package), we want to use the safe-charsets coding system property for this; but if we try to set that under 21.4, we get an error in C. I think I’m going to modify the latin-euro-standards package to check for that error, and to specify the safe-charsets property correctly if it is absent. This should eliminate the test failures, and should mean that query-coding-region works better for those coding systems. -- ¿Dónde estará ahora mi sobrino Yoghurtu Nghe, que tuvo que huir precipitadamente de la aldea por culpa de la escasez de rinocerontes? _______________________________________________ XEmacs-Buildreports mailing list [email protected] http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-buildreports