URL:
<https://savannah.gnu.org/bugs/?62816>
Summary: rename the \& escape...again
Project: GNU troff
Submitter: barx
Submitted: Tue 26 Jul 2022 08:57:58 AM CDT
Category: Core
Severity: 1 - Wish
Item Group: Documentation
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Tue 26 Jul 2022 08:57:58 AM CDT By: Dave <barx>
In short, no one seems happy with how the docs currently identify it:
non-printing input break.
Discussion about this has ranged across numerous threads, so this bug is
intended to serve as a centralized pointer to all the comments made so far. A
(probably incomplete) rundown of them is:
* http://lists.gnu.org/r/groff/2020-07/msg00098.html (continued at
http://lists.gnu.org/r/groff/2020-08/msg00014.html)
* bug #58933
* http://git.savannah.gnu.org/cgit/groff.git/commit/?id=36b5c885
* http://lists.gnu.org/r/groff/2022-05/msg00009.html (continued, at length, at
http://lists.gnu.org/r/groff/2022-06/msg00004.html)
* http://lists.gnu.org/r/groff/2022-07/msg00083.html
(Some of these threads started out as other topics, so I picked the point
where the topic of \&'s name came up, so that reading forward in a thread will
be on topic but not reading backward. From these anchor points, some threads
talk about both \& and other topics, so there's still some wading through
unrelated material required, if anyone's masochistic enough to to try read the
whole thing.)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62816>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
