Re: bug with start-process and start-process-shell-command

Mike> I think XEmacs should set useful defaults depending on the Mike> locale used in the system when XEmacs was started. Mike> I don't want that Mike> (set-language-environment "Japanese") Mike> sets ja_JP.eucJP locale again. We'll have to have Ben explain that. I have no idea what the rationale for that is. Given that most of that function seems to be intended to deal with Windows variance, possibly the whole thing is wrong-headed for Unix. Mike> I have only LANG set, I have neither set any LC_* variables Mike> nor LC_ALL, I had set these as well I probably would have to Mike> remember and restore them as well. No, LANG is the only variable touched by that code AFAICT. LC_* should be safe from it. Mike> It is very strange that such a lot of setup is needed in Mike> ja_JP.UTF-8. Not at all strange, actually. There's just zero data for dealing with ja_JP.UTF-8 in lisp/mule/japanese.el. Mike> Maybe most of that could be set correctly by default? Sure, but probably not soon if Ben or I have to do the work. I do think it's appropriate to figure out sane general semantics for `set-language-environment'. But with respect to language-specific settings, patches to the mule/LANGUAGE.el files are welcome, of course, but with the APIs changing we can't guarantee that they'll continue to work. You're welcome to lobby Ben if you like, but I don't think nitty gritty details of specific environment settings are a high priority right now with lots of things being very unstable. Ben has several unpublished workspaces that really need to be integrated before we start on complex configuration. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.