tags 541147 wontfix
thanks
On Wed, Aug 12, 2009 at 02:10:46AM +0300, Jari Aalto wrote:
> An examples, trying to get more information, putting the lintian
> message in double quotes:
>
> $ echo "W: wcd: manpage-has-errors-from-man usr/share/man/man1/wcd.1.gz 1:
> warning: `PU' not defined" | lintian-info
> <line hangs>
>
> Oh, there is backtick....
>
> SUGGESTION:
>
> Please present inly single quote characters in messages, that is, avoid use
> of:
>
> `text'
>
> and use
>
> 'text'
I don't intend to change this, for the following reasons:
* It is just as easy, if not easier, and more secure to run
'lintian-info' on its own and then just paste error messages into
its stdin. I've always used lintian-info this way. If you do this
then you don't have to worry about shell metacharacters in error
messages. I don't think it's reasonable to constrain groff to not
emit shell metacharacters on stderr (which would include $ as well
as `, for instance).
* ' is itself a shell metacharacter; you happen not to encounter this
because you're quoting with ", but not everyone will do that. I
don't think groff should be optimised for one particular way to pass
its error messages to lintian-info. :-)
* http://www.gnu.org/prep/standards/html_node/Quote-Characters.html
explicitly recommends this method of quoting in the C locale, and
groff is a GNU package. (I'm aware that not everyone likes this; I
do not intend to engage in debate about the correctness of the GNU
Coding Standards here ...)
If upstream wish to do otherwise, then that's up to them, but I'm not
going to override them.
Regards,
--
Colin Watson [[email protected]]
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
