[bug #64155] [troff] specifying -fZD on command line generates warnings

Follow-up Comment #45, bug #64155 (group groff): [comment #44 comment #44:] > I suspect you're not using _echo_(1) the way you think you are. I admit I didn't consider its portability, but on my system it output what I intended. > Because the default style is 'R', and the font 'ZDR' exists (on >

[bug #64155] [troff] specifying -fZD on command line generates warnings

Follow-up Comment #44, bug #64155 (group groff): [comment #43 comment #43:] > A vast improvement! > > But maybe a little _too_ quiet: groff disregards the -fZD flag without telling the user it's doing so. > > echo "\N'110'" | groff -ww -fZD > > This fails to load the ZD family (because there is

[bug #64155] [troff] specifying -fZD on command line generates warnings

Follow-up Comment #43, bug #64155 (group groff): [comment #41 comment #41:] > Now: > > $ echo | ./build/test-groff -fZD -a > A vast improvement! But maybe a little _too_ quiet: groff disregards the -fZD flag without telling the user it's doing so. echo "\N'110'" | groff -ww -f

[bug #64155] [troff] specifying -fZD on command line generates warnings

Follow-up Comment #42, bug #64155 (group groff): So here's what got lost last week. I did in fact implement a string comparison conditional operator in GNU _troff_ in my working copy. And it worked. $ git stash show -p 1 diff --git a/src/roff/troff/input.cpp b/src/roff/troff/input.cpp index 8d

[bug #64155] [troff] specifying -fZD on command line generates warnings

Update of bug #64155 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed ___ Follow-up Comment #41: I'll follow up with a

[bug #64155] [troff] specifying -fZD on command line generates warnings

Update of bug #64155 (group groff): Status: Confirmed => In Progress ___ Follow-up Comment #40: I have a fix for this involving something old and in plain sight. ___

[bug #64155] [troff] specifying -fZD on command line generates warnings

Follow-up Comment #39, bug #64155 (group groff): Self-followup: [comment #37 comment #37:] > in a way back compatible to almost any older troff. Obviously, this specific example is not AT&T-portable due to the long names, but the logic can be written portably. _

[bug #64155] [troff] specifying -fZD on command line generates warnings

Follow-up Comment #38, bug #64155 (group groff): [https://savannah.nongnu.org/support/?111059 Frustration submitted.] ___ Reply to this item at: ___ Mes

[bug #64155] [troff] specifying -fZD on command line generates warnings

Follow-up Comment #37, bug #64155 (group groff): [comment #34 comment #34:] > Maybe it is time for a proper string equality operator in our > conditional expressions. While that would be a useful addition to the language, equivalent functionality can be achieved in user space, in a way back compa

[bug #64155] [troff] specifying -fZD on command line generates warnings

Follow-up Comment #36, bug #64155 (group groff): Sigh. Wrote a long comment. Form was stale. Document Expired. Text lost. ___ Reply to this item at: ___

[bug #64155] [troff] specifying -fZD on command line generates warnings

Follow-up Comment #35, bug #64155 (group groff): [comment #34 comment #34:] > > > Well, when you're prepared to discuss it, it would be good to know if/how Dave's original report in comment #0 was invalid > > > > I think I can answer this - it is certainly not invalid, it just has nothing to do w

[bug #64155] [troff] specifying -fZD on command line generates warnings

Follow-up Comment #34, bug #64155 (group groff): commit 604361951c9ddad621b3e0786ca7a2946e212842 Author: G. Branden Robinson Date: Fri May 3 00:00:59 2024 -0500 Revert "[troff]: Validate a font family before using it." This reverts commit 39ffa368dc6a1de4c11cf3f4f5b8594d3c974173.

[bug #64155] [troff] specifying -fZD on command line generates warnings

Follow-up Comment #33, bug #64155 (group groff): [comment #32 comment #32:] > [comment #28 comment #28:] > > [comment #27 comment #27:] > > Specifically, am I correct to claim either of the following? > > > > A. "[G]iven that mom has her own system of managing fonts, and part of her contract wit

[bug #64155] [troff] specifying -fZD on command line generates warnings

Update of bug #64155 (group groff): Category: Font - others/general => Core Status: Need Info => Confirmed Summary: specifying -fZD on command line generates warnings => [troff] specifying -fZD on c