[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #54475] hdtbl.tmac-u: String variable 't*held' is not defined when
Bjarni Ingi Gislason
[bug #54475] hdtbl.tmac-u: String variable 't*held' is not defined when used
Wed, 15 Aug 2018 18:15:21 -0400 (EDT)
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Follow-up Comment #2, bug #54475 (project groff):
My text is not shown on the web site, probably because I forgot to add the
troff: warning: macro 't*held' not defined
From the file "contrib/hdtbl/hdtbl.tmac-u"
. ds t*held \\*[t*held] t*hold\\n[t*numb] \\n[dn]\"
The request '.as' is the right one to use here.
A comment to comment #1:
troff issues a warning for a "groff" code in the repository. Why is that not
a issue for the bug tracker?
What is the "Item Group" "Wishlist" doing in a bug tracker?
Is bad (worse) programming practice considered a issue for a bug tracker or
rather only for the discussion list, or even banned?
Why are style issues considered by some people to be in the category af a
The only "no effort to find", is doing nothing.
"Anybody can ..." but fact is that practically nobody has done or does it.
Why do you (plural and Ingo) not always (maybe practically never) run groff
with "-ww -b" (including inside "man" and "Makefiles")?
Deleting issues (except "foreign" stuff) from a bug tracker is falsifying
facts and history.
Using undefined items is a bad programming practice and there is no
obligation to use them that way.
Why is groff not the primary, mandatory model for all other programming
languages for using undefined variables?
Is bad (worse) programming practice a "bug" and if not, why not always use
these programming practices irrespecitve of its influence now and in the
future (including stealing peoples time)?
Why does "groff" not have a quality rules about code and documentation?
Reply to this item at:
Message sent via Savannah