Before using pyxf86config, the keyboard part of my XF86Config file looked like: # If you'd like to switch the positions of your capslock and # control keys, use: # Option "XkbOptions" "ctrl:nocaps" #Option "XkbOptions" "" Identifier "Keyboard0" Driver "keyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "us" #Option "XkbVariant" "" But afterwards, it looks like: # If you'd like to switch the positions of your capslock and # control keys, use: # Option "XkbOptions" "ctrl:nocaps" #Option "XkbOptions" "" Identifier "Keyboard0" Driver "keyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "us" #Option "XkbVariant" "" As you can see, the commented-out line for XkbVariant is no longer on it's own line. The XF86Config file works just fine, but this doesn't seem like the desirable behavior. Also, if the XkbVariant line is not commented out, then the EOL is preserved. So it must have something to do with the next line starting with a '#'...
This is a "bug" in libxf86config. It thinks that everything that is a comment after an option is a comment about that line. Then when it prints it out it places it right after the option. I've been irritated by this too. I'm reassigning to xlibs. mharris, I doubt you want to prioritize this, but maybe you can bring it up upstream?
Hmm. Indeed, if it is a libxf86config bug, it could potentially be odd to correctly fix. I'll report it upstream so that we can go with whatever they decide is a proper fix by them, and maintain compatibility, etc.
Also, just a note, this is low priority and likely won't be fixed for our final release, unless someone provides a patch from upstream. There are far too many much more important bugs needing fixing for now.
Pinged upstream today about this.
This issue is fixed in CVS now, but I haven't updated to the fixed version yet.
XFree86-4.2.99.3-20030115.0 build contains these fixes. Setting to MODIFIED and awaiting confirmation of fix.
Yup, this is fixed now. Thanks for your help.