Path: csiph.com!3.us.feeder.erje.net!feeder.erje.net!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail From: Dave Newsgroups: gnu.groff.bug Subject: [bug #57538] -me macros: incorrect postscript output of macro .(b Date: Sat, 4 Jan 2020 21:01:38 -0500 (EST) Lines: 37 Approved: bug-groff@gnu.org Message-ID: References: <20200104-141245.sv93119.1279@savannah.gnu.org> <20200104-152023.sv93119.4969@savannah.gnu.org> <20200104-200138.sv93119.80713@savannah.gnu.org> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain;charset=UTF-8 X-Trace: usenet.stanford.edu 1578189703 21105 209.51.188.17 (5 Jan 2020 02:01:43 GMT) X-Complaints-To: action@cs.stanford.edu To: Dave , bug-groff@gnu.org Envelope-to: bug-groff@gnu.org X-PHP-Originating-Script: 1001:sendmail.php X-Savane-Server: savannah.gnu.org:443 [2001:470:142:5::79] X-Savane-Project: groff X-Savane-Tracker: bugs X-Savane-Item-ID: 57538 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0 X-Apparently-From: 2605:a601:aac3:e300:55b7:e0e9:96ca:b482 (Savane authenticated user barx) In-Reply-To: <20200104-152023.sv93119.4969@savannah.gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.79 X-BeenThere: bug-groff@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Bug reports for the GNU version of nroff, troff et al" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <20200104-200138.sv93119.80713@savannah.gnu.org> X-Mailman-Original-References: <20200104-141245.sv93119.1279@savannah.gnu.org> <20200104-152023.sv93119.4969@savannah.gnu.org> Xref: csiph.com gnu.groff.bug:1603 Follow-up Comment #2, bug #57538 (project groff): Additionally, the thread mentioned in comment #1 continued for a bit off-list when Deri emailed me some PDF attachments he couldn't easily send to the list. And thanks to his work, I've been able to home in a little more on this bug. Because as it turns out, while the bug was in groff 1.21, and is in current groff, it has not been in every version of groff released in between. I'm not sure which all official releases it appears in -- it is absent in at least 1.22.2 and 1.22.3 -- but I've iterated through the various versions of tmac/e.tmac / tmac/e.tmac-u (the file was renamed at some point) to find out exactly where it came and went. The bug disappeared in commit b6906269 of this file and reappeared in commit 98b028d6. But the interesting thing about this is that these commits also respectively introduced and then removed another bug. As documented, all "displays" in -me (of which ".(b" is one) should have space corresponding to the \n(bs register above and below; the test case at hand explicitly sets this register to 0, specifying no extra space above or below the block. But starting with commit b6906269, this test case began emitting an extra line above the .(b block; commit 98b028d6 fixed this. So somehow this extra-space bug removed, or at least masked, the page-break bug as a side effect. _______________________________________________________ Reply to this item at: _______________________________________________ Message sent via Savannah https://savannah.gnu.org/