Follow-up Comment #2, bug #67570 (group groff): [comment #1 comment #1:] > I notice I forgot something in the new `pchar` request: > > It should try to resolve the argument as a character class first.
I don't see why. The .class request doesn't define a character, so one
wouldn't expect .pchar to analyze it as a character. And as the manual says,
"Currently, only the 'cflags' request can handle references to character
classes." So even if .pchar did return something for it, the only data points
it could return are the characters in the class and its set of flags, as
that's the only data a character class can hold.
This might be marginally useful, but it'd be a surprising use for .pchar
rather than a separate request, say, .pclass (although the two sharing a
namespace does muddy this some).
> $ printf '.class [EOS] \\[em]\n.pchar [EOS]\n'
Because the class name contains the ] character (as recommended in the manual
to avoid namespace collisions), it has to be dereferenced with the \C escape,
so the above .pchar syntax doesn't access the class anyway.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67570>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
