[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

URL: Summary: Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7) Project: GNU troff Submitted by: barx Submitted on: Thu 13 May 2021 02:45:39 PM CDT Category: Core

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Update of bug #60602 (project groff): Status:None => Confirmed Assigned to:None => gbranden ___ Follow-up Comment #1: Question 1: Which of

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Update of bug #60602 (project groff): Status: Confirmed => Fixed Open/Closed:Open => Closed Planned Release:None => 1.23.0

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Follow-up Comment #3, bug #60602 (project groff): [comment #1 comment #1:] > Rule #1 of the Murray Hill Unix Room was: don't write comments. > > But if you do, remember Rule #2: make them misleading. And I presume Rule #3 was "see Rule #3" in order to set up an infinite loop that prevented any s

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Follow-up Comment #4, bug #60602 (project groff): > because I have nothing that can interpret the Graphic Systems C/A/T command stream the former produces. I do : $ cat2dit -Tps < output.cat | grops

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Follow-up Comment #5, bug #60602 (project groff): Hi, John! [comment #4 comment #4:] > > because I have nothing that can interpret the Graphic Systems C/A/T command stream the former produces. > > I do

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Follow-up Comment #6, bug #60602 (project groff): > Now all I need is a way to get V7 troff CAT output out of the SIMH instance I'm running. > […] > Maybe I can od(1) it and then parse it back into a real stream. That's exactly what I do. I use this

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Follow-up Comment #7, bug #60602 (project groff): [comment #6 comment #6:] > > Now all I need is a way to get V7 troff CAT output out of the SIMH instance I'm running. > > […] > > Maybe I can od(1) it and then parse it back into a real stream. > > That's exactly what I do. I use this

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Follow-up Comment #8, bug #60602 (project groff): > Excellent! Except...maybe my JS environment is too old? `Array.prototype.flat` was only added to the ECMAScript spec in 2019, so it's possible your version of Node.js is outdated. If your distro's lagging behind (i.e., upgrading doesn't help),

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Follow-up Comment #9, bug #60602 (project groff): I don't have any analysis yet, but here's a C program to undump "od -b". #include // bool, false, true #include // feof(), getline(), stdin, fprintf(), stderr, perror() #include // malloc(), free(), exit(), EXIT_FAILURE, EXIT_SUCCESS #include

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Follow-up Comment #10, bug #60602 (project groff): CSTR 54 is correct. Branden's 'guess' is wrong and no change from Bell Labs troff's normal and documented behaviour should be made based on it. vflag is used to indicate the motion is vertical. It is nothing to do with forcing a unit calculatio

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Follow-up Comment #11, bug #60602 (project groff): To make the record here complete: bug #61437 precipitated this issue being revisited and the conclusion of comment #1 overturned. ___ Reply to this item at:

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Follow-up Comment #12, bug #60602 (project groff): Hi John, I had this sitting in a browser text box for days, so I'm just going ahead and pushing it out to record the state of things. [comment #4 comment #4:] > > because I have nothing that can interpret the Graphic Systems C/A/T command stream

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Follow-up Comment #13, bug #60602 (project groff): [comment #10 comment #10:] > CSTR 54 is correct. Branden's 'guess' is wrong and no change from Bell Labs troff's normal and documented behaviour should be made based on it. vflag is used to indicate the motion is vertical. It is nothing to do w

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Follow-up Comment #14, bug #60602 (project groff): > this GitHub project seems not to have been updated in a while (December 2019, IIRC), and Node itself has moved on. That's not how things work in the JavaScript world. ECMAScript, unlike Python, is designed to remain compatible with all existing

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Follow-up Comment #15, bug #60602 (project groff): > In fact, a C version of cat2dit that would run on V7 Unix under SIMH would, in my imagination, kick ass. (People really wanted one, back in the '80s.) Then there would be no data migration issue or octal dumping to mess with. Run SIMH in a te

[bug #60602] Unit discrepancy in \r, \u, and \d between Texinfo manual and groff(7)

Update of bug #60602 (project groff): Status: Fixed => Invalid Planned Release: 1.23.0 => None ___ Follow-up Comment #16: This turned out to b