User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0)
            Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
References: <jqa6j8$vge$1@dough.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID:  <4FC8E9E6.2090202@morningstar2.co.uk>
Date:         Fri, 1 Jun 2012 17:12:22 +0100
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@listserv.uni-heidelberg.de>
Sender: Mailing list for the LaTeX3 project <LATEX-L@listserv.uni-heidelberg.de>
From: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: xparse -- Warning "xparse/redefine-command"
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <jqa6j8$vge$1@dough.gmane.org>
Precedence: list
Status: R

On 01/06/2012 11:47, Marco Daniel wrote:
> Hi,
> 
> If you use the command \DeclareDocumentCommand and the command name
> already exists, you will get the warning "LaTeX warning
> "xparse/redefine-command" " initialized by
> 
> \msg_kernel_warning:nnxx { xparse } { redefine-command }
> 
> 
> I think most package authors will use this command. (e.g. fontspec)
> 
> Based on this fact you will get a lot of warnings. In my opinion
> warnings become ineffectually.
> 
> So I suggest to use \msg_kernel_info:nnxx { xparse } { redefine-command }
> 
> What do you think?

This is 'by design'. The reasoning is that altering an existing command
potentially changes the interfaces defined in a document, and so
deserves a warning in the log. You can of course redirect these warnings
to info before loading xparse, if you feel this is appropriate.
--
Joseph Wright