Yves-Alexis Perez <cor...@debian.org> writes: > On jeu., 2011-11-17 at 13:19 -0800, Russ Allbery wrote:
>> Well, hopefully one would only use the default behavior when loading >> the user's personal configuration (and maybe system-wide defaults), >> where cpp is part of the expected interface. > Well, it seems that -nocpp was used since a long time, so “expected > interface” doesn't really stand here. Well, for Xfce, yes, but I think every other desktop environment uses the defaults. At least, I was switching from GNOME and can confirm that it definitely uses the preprocessor when parsing the user's .Xresources, since that's what triggered the original bug, and I know it also worked with WindowMaker and OpenSTEP. I haven't tested KDE. Also, it's the default behavior if you're not using a desktop environment (which admittedly is getting rare). I don't *think* you're likely to run into any backward compatibility problems by removing -nocpp from Xfce. I can't think of an otherwise valid .Xresources file that would then break. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
