On Tuesday, April 18 2006 22:59, Daniel Stone wrote: > On Tue, Apr 18, 2006 at 11:35:37PM +0200, Denis Barbier wrote: > > On Tue, Apr 18, 2006 at 11:40:31AM +0300, Daniel Stone wrote: > > > On Tue, Apr 18, 2006 at 05:02:12AM +0300, Shai Berger wrote: > > > > Then I tried the other method referred to in xkb-data's > > > > README.Debian, that of passing a -xkbdir to the server. The server > > > > did not recognize this flag (and gave me a list of the flags it did > > > > recognize...). > > > > > > I removed most of the XKB command-line options upstream. > > It's not for security reasons, it's because I don't believe it has any > place on the command line. Config file, maybe, but why command line?
Well, I'm not an X Server developer, but I can see the usefulness of controlling the xkb directory in the invocation of the X Server -- for trying things out, or for user-specific features. As things are documented, this should be doable without the command-line option -- via the environment variable, that is, $ startx -- :3 -xkbdir XXX should be equivalent to $ XKBPATH=XXX startx -- :3 And the way I see things, it is indeed "equivalent" -- the environment variable is ignored. Did you remove this also? If so, how can I make the X Server use a different xkb directory? If not, why not? The same reasoning should apply as for the command-line option. Thanks, Shai. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]