Path: utzoo!attcan!uunet!lll-winken!ames!think!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: XrmParseCommand and command flags
Message-ID: <8904091921.AA02145@EXPIRE.LCS.MIT.EDU>
Date: 9 Apr 89 19:21:00 GMT
References: <760@stan.stan.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 16


   One way around the problem is for the application to superimpose an options
   table onto the option tables already in use.  However, this implies that the
   application will have be modified to use the resource manager mechanism to
   get/check for arguments, since they will be stripped out of argv.

For options carrying an argument, you can use XrmoptionSkipArg to avoid having
them stripped out of argv.  There really ought to be some way of keeping a
singleton option from being stripped (XrmoptionSkipNoArg?), as well as some way
of keeping an option with more than one argument (XrmoptionSkipNArgs?).
Perhaps you'd like to develop a proposal...

   Is there some easy way to disable the prefix matching in the resource
   manager?

Nope.