Path: utzoo!utgpu!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!vsi1!wyse!x2!mikew From: mikew@x2.wyse.com (Mike Wexler) Newsgroups: comp.windows.x Subject: Conflict between XrmParseCommand and XSetCommand Message-ID: <1721@wyse.wyse.com> Date: 27 Sep 88 18:41:43 GMT Sender: news@wyse.wyse.com Reply-To: mikew@x2.wyse.com (Mike Wexler) Organization: Wyse Technology Lines: 11 I have found what seems to be a conflict between these two functions. XrmParseCommand will usually be run before the XOpenDisplay to get the display argument. XrmParseCommand removes much of the information from the command line. XSetCommand can't be run until after the XOpenDisplay, but needs to have a complete command line. Is there some way around this other than to make a complete copy of the argv array and its contents? Mike Wexler(wyse!mikew) Phone: (408)433-1000 x1330 Moderator of comp.sources.x