[comp.windows.x] Conflict between XrmParseCommand and XSetCommand

mikew@x2.wyse.com (Mike Wexler) (09/28/88)

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

swick@ATHENA.MIT.EDU (Ralph R. Swick) (09/28/88)

     Date:  27 Sep 88 18:41:43 GMT
     From:  vsi1!wyse!x2!mikew@AMES.ARC.NASA.GOV  (Mike Wexler)

     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?

I can't think of one.  This is exactly what Xt does.