Follow-up Comment #35, bug #63074 (group groff): Deri persuaded me not to go one of the directions I headed.
Which is fine, because that puts me back on a path I wanted to be on anyway:
copy mode (or an ersatz simulacrum thereof) for `\X`.
commit a1ced0efe59519afa0aa00e049b7ef6f3627260f
Author: G. Branden Robinson <g.branden.robin...@gmail.com>
Date: Sat Sep 7 20:01:10 2024 -0500
Revert "[troff]: \X maps some basic Latin chars to specs."
This reverts commit dcae60b0fb1ad3fa3314fdfdbecb973961a40410.
Reverting the change better simulates copy mode, which is eventually
where we want to take `\X`'s interpretation of its delimited argument.
There's simply no convenient infrastructure for that in "input.cpp" yet.
Output drivers that need to distinguish characters in device extension
commands destined for "document text" from those intended for
"application text" (or some other external purpose, like constructing a
shell command for execution) have to use out-of-band means to achieve
this distinction. Documentation of recommended practices for achieving
this are being hashed out and will soon, it is hoped, be documented.
Fixes <https://savannah.gnu.org/bugs/?66165>. Thanks to Deri James for
the report.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63074>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
