[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Confusing error message in development version

From: Jacob Bachmeyer
Subject: Re: Confusing error message in development version
Date: Mon, 11 Oct 2021 23:25:13 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20090807 SeaMonkey/1.1.17 Mnenhy/

Patrice Dumas wrote:
On Mon, Oct 11, 2021 at 06:28:33PM +0200, Patrice Dumas wrote:
On Mon, Oct 11, 2021 at 04:30:20PM +0100, Gavin Smith wrote:
Git revision a9aacb0b39967059b8064

If I use a non-existent customization variable, like

./texi2any.pl  test.texi -c OPEN_CODE_QUOTE=\`

the error message is

texi2any: warning: GNUT_set_from_cmdline: unknown variable OPEN_CODE_QUOTE

The reference to GNUT_set_from_cmdline is confusing so whatever this is it
should be removed from the error message.  I'll look into it myself if I
have time.
It is a bug, the GNUT_set_from_cmdline is supposed to be some context
for translation, as this message can happen in diverse places.  I must
have used the wrong function of misued the perl gettext API.

Actually it was probably simply an oversight.  Note that I have kept the
function names in other warning messages, as either it is useful to have
the function name as the user should have used the function or the
message should not actually happen, it is more like a bug.  I am not
100% sure on the second case, but these messages are not supposed to
happen in normal cases.

What about making the message unique? "unknown variable set on command line: OPEN_CODE_QUOTE"?

-- Jacob

reply via email to

[Prev in Thread] Current Thread [Next in Thread]