> \providecommand has uses, of course, and this could be one of them, but it
> should not be used indiscriminately. However, if users feel the need to
> change that color, maybe the right thing to do is making it configurable,
> in a way or another,
For this case we already have an enhancement request. Nevertheles, it was only an example what could
happen. In principle users might change every command definition. When we use \newcommand the import
of TeX documents would then lead to uncompilable documents.
> possibly testing whether it was already defined.
That would be the \...@undefined solution but \providecommand does nearly the same: only when a command
is not already defined, the new definition is used.
>> tex2lyx already recognizes \providecommand. We are currently working on a
>> better solution for the tex2lyx preamble handling to assure that roundtrips
>> will work in as many as possible cases. The change from \newcommand is the
>> first step.
>
> The wrong step, I would say.
Could you please be more precise?
regards Uwe