Re: check process state before accessing coding_stream (fix PR#1061)

dv> Martin R Buchholz wrote: dv> X resources are a not very good mechanism which, what's more, dv> works only under X. If you start under X, won't you get X resources globally for that kind of thing (menubar strings), regardless of which platform the frame is on? Or does that depend on how the resources for the frame get initialized? Some of the relevant variables are globals (or specifiers, whose default could be set up to act like a global for strings in menu items, etc), aren't they? If not, then wouldn't it be possible for your XEmacs to pick up X resources for X frames and Windows resources for Windows frames, and if it was a global variable being set, this could change X settings simply because you opened a Windows frame or vice versa? That would be really evil. dv> The gettext'ization of the Lisp strings should be something dv> generic, not depending on the platform your XEmacs frame is dv> on. San-sei. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."