List of CLI commands.
ajax.criterion at gmail.com
Tue Mar 27 19:42:46 CEST 2012
I don't have an issue with the configs being in xml format, it's a
widely used format and is similar to html (for obvious reasons), which
I have some experience with. Given that many of the config files are
describing the layout of objects in a GUI, it makes sense to me to use
it. If the configs were in plain text I think it would be more
confusing in the end, and you would have to have yet another layer of
translation between the plain text and the binaries in order to apply
the configs in the interface. That's my two cents, but of course I
don't speak on behalf of the developers.
On Tue, Mar 27, 2012 at 9:21 AM, Ray Andrews <rayandrews at eastlink.ca> wrote:
> On 27/03/12 07:53 AM, Ahau @porteus.org wrote:
>> Is this what you're looking for?
> Thanks, that is a help. But I can find no link to that page from it's
> And there is still the question of a list of all the CLI tools, not just
>> --prepared for 4.6 but probably the same or quite similar for 4.8
>> or, the man page for xfconf-query:
>> I've done very little with xfconf-query myself, I typically manually
>> edit the xml files (yes, I know this is not recommended, but if I were
>> to do more mods by scripts, I'd probably force myself to learn it.
> So we have that in common, we both want to be able to manually edit
> config files, which is why I'm so interested to find out why they are
> as xml not plain text.
> Xfce mailing list
> Xfce at xfce.org
More information about the Xfce