bug-groff
[Top][All Lists]
Advanced

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

[bug #62814] consolidate or distinguish tty.tmac and tty-char.tmac


From: Dave
Subject: [bug #62814] consolidate or distinguish tty.tmac and tty-char.tmac
Date: Mon, 25 Jul 2022 22:19:43 -0400 (EDT)

URL:
  <https://savannah.gnu.org/bugs/?62814>

                 Summary: consolidate or distinguish tty.tmac and
tty-char.tmac
                 Project: GNU troff
               Submitter: barx
               Submitted: Mon 25 Jul 2022 09:19:42 PM CDT
                Category: Macro - others/general
                Severity: 1 - Wish
              Item Group: Feature change
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Mon 25 Jul 2022 09:19:42 PM CDT By: Dave <barx>
As discussed in the thread starting at
http://lists.gnu.org/r/groff/2022-07/msg00041.html, it is unclear what utility
is served by having tmac/tty-char.tmac
<http://git.savannah.gnu.org/cgit/groff.git/tree/tmac/tty-char.tmac> loaded in
different circumstances from tmac/tty.tmac
<http://git.savannah.gnu.org/cgit/groff.git/tree/tmac/tty.tmac>.

troffrc unconditionally loads tty.tmac when the postprocessor is
grotty--congruent with how it handles other postprocessors--so it's only
tmac/tty-char.tmac that might not be loaded for some terminal output.

It seems that these files should always be loaded in tandem (whether by
loading both files, or combining the files' content into one), or a use case
for using tty.tmac without tmac/tty-char.tmac documented.

Presently, both files contain (disjoint) sets of tty fallback character
definitions.  As Branden and I agreed in the email thread, all fallback
character definitions should live in the same place, wherever ends up making
the most sense for that.

For modularity, tty-char.tmac could continue to be its own file for this
purpose, separating these definitions from other terminal-setup tasks that
tty.tmac performs.  But if so, and absent a demonstrable (and preferably
documented) use case for not loading these definitions, it seems tty.tmac
ought to unconditionally include tty-char.tmac.

(One item from the email discussion has been resolved: Branden wrote "I think
that definition [of "\[sd]"] in tty-char.tmac should be dropped," and this was
done in commit 175c42d7
<http://git.savannah.gnu.org/cgit/groff.git/commit/?id=175c42d7>.)







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62814>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

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