bugGNU roff - Bugs: bug #54475, hdtbl.tmac-u: String variable...

 
 

bug #54475: hdtbl.tmac-u: String variable 't*held' is not defined when used

Submitter:  Bjarni Ingi Gislason <bjarniig>
Submitted:  Wed 08 Aug 2018 10:34:50 PM UTC
   
 
Category:  Macro - others/general Severity:  2 - Minor
Item Group:  Warning/Suspicious behaviour Status:  Duplicate
Privacy:  Public Assigned to:  gbranden
Open/Closed:  Closed Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 11 Jan 2022 11:09:55 AM UTC, comment #3: 

Closing as duplicate of (the later) bug #55732.

G. Branden Robinson <gbranden>
Group administrator
Wed 15 Aug 2018 10:15:20 PM UTC, comment #2: 

+verbatim+
  My text is not shown on the web site, probably because I forgot to add the "-verbatim-" line:

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 bug.

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?
-verbatim-

Bjarni Ingi Gislason <bjarniig>
Thu 09 Aug 2018 07:08:52 PM UTC, comment #1: 

Please refrain from littering the bugtracker with reports that require absolutely no effort to find.  Anybody can run groff with warning options enabled, and finding potential issues that way actually causes less effort than finding them in the bug tracker.

As a rule, reporting a compiler warning in the bugtracker is detrimental unless there is reason to believe that there is an actual bug.

In this case, there is clearly no bug because the language specification says that it is valid to use an undefined string in order to define it to be empty.

If somebody with higher privilege than myself sees an option to completely delete issues (as opposed to merely closing them). please consider deleting this and similar issues, because even when closed, it still pollutes the database and makes searching for past issues gratuitously harder.

Does anybody know what the consequences of flagging issues as "spam" are?  That might be appropriate, too, but i'm not sure.

Ingo Schwarze <schwarze>
Group Member
Wed 08 Aug 2018 10:34:50 PM UTC, original submission:  


Subject: hdtbl.tmac-u: String variable 't*held' is not defined when used

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.

Bjarni Ingi Gislason <bjarniig>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by gbranden (Posted a comment)
  • -email is unavailable- added by bgarrigues (Updated the item)
  • -email is unavailable- added by schwarze (Posted a comment)
  • -email is unavailable- added by bjarniig (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 8 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-01-11 gbranden StatusNone Duplicate
        Assigned toNone gbranden
        Open/ClosedOpen Closed
    2018-11-26 bgarrigues Severity1 - Wish 2 - Minor
        Item GroupFeature change Warning/Suspicious behaviour
    2018-08-09 schwarze CategoryNone Macro - others/general
        Severity3 - Normal 1 - Wish
        Item GroupBuild/Installation Feature change

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code