LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Fri, 1 Jun 2012 17:12:22 +0100
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID: <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=ISO-8859-1
From: Joseph Wright <[log in to unmask]>
Parts/Attachments: text/plain (26 lines)
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