Follow-up Comment #6, bug #67837 (group groff): [comment #5 comment #5:] > That's the info I'm requesting of you.
OK, thanks for clarifying.
> It's a debugging request. We don't enumerate everything `pev`
> reports, either, and never have.
And now _I_ must clarify. The manual need say nothing about the output of
.pchar itself.
But the info .pchar reports means something. .pchar reports it because it
affects groff behavior. And we had a long debate in bug #67711 about what
that effect was supposed to be--because it's undocumented. We both lamented
that fact in the debate, in fact. Hence this ticket to lessen our
lamentations.
> I need to know what it is you expect me to say about the "flag
> interaction of character class and individual character".
In a nutshell, that character flags assigned to a character class are
effectively logically ORed with the flags of each character in the class.
Your "what time" questions are valid and demand answers for a full accounting
in the manual. But even mentioning the logical OR without those crucial
details would be an improvement over the status quo, which doesn't mention the
ORing _at all_. A single vague sentence could have forestalled a swath of
that #67711 thread.
If you want to wait for a full understanding behind the scenes before
breathing a word of this to the audience, that's a defensible position. But,
as I've apparently become fond of saying lately, perfect is the enemy of good.
I think it's better to give a vague gesture toward what's happening, with
details to be filled in later, than to keep mum about it. The manual was
vague about a lot of details for decades before your reign of
terror^Wreformation began, but people still found it useful.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67837>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
