Follow-up Comment #2, bug #67837 (group groff):
[comment #1 comment #1:]
> Can you deploy the newly enhanced `pchar` request against bug #67571?
Sure, but if we agree that the discrepancy reported there is not rationally
defensible (or, in your words there, is "damnable as all hell")--that is, that
it must be a bug--then it's not relevant to this documentation issue. (That
is, it could be a useful troubleshooting tool for #67571, but seems to have no
bearing on the present bug.)
> The enhanced `pchar` request now distinguishes flags "inherent"
> to the character from those absorbed via class membership.
Right, and it's this absorption that is undocumented. Even updating the docs
to mention how one achieves the "effective flags" .pchar is already reporting
would be an improvement.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67837>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
