Bug 9947 - XmbLookupString man page warning
Summary: XmbLookupString man page warning
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 7.1 (2006.05)
Hardware: Other All
: low minor
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL: http://bugs.debian.org/cgi-bin/bugrep...
Whiteboard: 2011BRB_Reviewed
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-11 01:52 UTC by Brice Goglin
Modified: 2018-06-12 19:05 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Brice Goglin 2007-02-11 01:52:52 UTC
Bug reported to the Debian BTS 2 years ago by Kevin Ryde, still valid.

Brice


"man XmbLookupString" produces a warning,
	/tmp/zmanE2taEp:218: warning: numeric expression expected (got `$')
Comment 1 Daniel Stone 2007-02-27 01:36:20 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 2 Jesse Adkins 2010-11-28 22:42:34 UTC
Works fine with the latest git. Assuming it got fixed.
Comment 3 Cyril Brulebois 2010-12-03 08:48:10 UTC
Hi Jesse,

I beg to differ:
-(jobs:1)-(cyril@talisker)-(~/debian-x/lib/libx11.git/man)-(master)
$ PAGER=cat man -l XmbLookupString.3 > /dev/null
<standard input>:217: warning: numeric expression expected (got `$')

Reopening accordingly.

I'm no *roff guru, but the culprit seems to be the .NT macro here:
| begins in the initial state of the encoding of the locale
| (if the encoding of the locale is state-dependent).
| .NT
| To ensure proper input processing,
| it is essential that the client pass only

in the generated XmbLookupString.3
Comment 4 Adam Jackson 2018-06-12 19:05:59 UTC
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.