Follow-up Comment #11, bug #62916 (group groff): [http://git.savannah.gnu.org/cgit/groff.git/commit/?id=fb6fdbd9d Commit fb6fdbd9d], an addendum to the fix for bug #66481, updated doc/groff.texi.in to note that a "future" groff "may deprecate" | as a delimiter. The log message of the later [http://git.savannah.gnu.org/cgit/groff.git/commit/?id=ec34f0171 commit ec34f0171] says that the delimiter | is "deprecated." So the delimiter | either: * is deprecated, in which case the info-manual text should be updated; * is not deprecated, in which case the ec34f0171 log message misspoke (but can't be corrected); or * exists in a quantum state of both deprecated and not deprecated, in which case the documentation should conditionally state one or the other depending on whether the cat is alive.
But in any of those cases, the deprecation belongs on the list this ticket contemplates. The fix for bug #66686 did _not_ note this about + (and perhaps other characters) as a delimiter. But the [http://git.savannah.gnu.org/cgit/groff.git/commit/?id=1eed3ccea commit 1eed3ccea] cited in that ticket seems to sweep it up in some text added to the info manual about a "delimiter character [that] is also meaningful when beginning a numeric expression," which "a future groff release may reject." So all such delimiters should be on this ticket's deprecation list. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?62916> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
signature.asc
Description: PGP signature
