[bug #64877] src/roff/groff/groff.1.man: use "-K enc" instead of "-k"

URL: Summary: src/roff/groff/groff.1.man: use "-K enc" instead of "-k" Group: GNU roff Submitter: bjarniig Submitted: Thu 09 Nov 2023 07:18:20 PM UTC Category: Core

[PATCH] Fix indxbib bogus size diagnostic

* src/libs/libbib/index.cpp (index_search_item::check_header) Fix size calculation typo that generated bogus diagnostic "lookbib: error: corrupt header in index file". --- ChangeLog | 7 +++ src/libs/libbib/index.cpp | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff

[bug #64319] [gropdf] migrate back to 'L<' template for unpack (Perl 5.9)

Update of bug #64319 (project groff): Summary: [gropdf] migrate back to 'L<' template for unpack => [gropdf] migrate back to 'L<' template for unpack (Perl 5.9) ___ Reply to this item at:

[bug #64879] [PATCH] [libbib] fix bogus size diagnostic

URL: Summary: [PATCH] [libbib] fix bogus size diagnostic Group: GNU roff Submitter: gbranden Submitted: Fri 10 Nov 2023 05:55:32 AM UTC Category: Preprocessor refer

[bug #64869] master branch, is the version from "nroff -v" always the same as from "groff -v"?

Update of bug #64869 (project groff): Status:None => Need Info ___ Follow-up Comment #1: Can you reproduce this problem with a stock _groff_ 1.23.0 checkout from Git? I don't think there

[bug #64862] [tbl] clobbers value of previously selected font

Follow-up Comment #1, bug #64862 (project groff): We _could_ solve this the way we save other things in tbl: by creating registers and laboriously populating and restoring from them. But there are a _lot_ of "previous-value" parameters that would require this approach. * previously selected font

[bug #64869] [bjarnigroff] master branch, is the version from "nroff -v" always the same as from "groff -v"?

Update of bug #64869 (project groff): Summary: master branch, is the version from "nroff -v" always the same as from "groff -v"? => [bjarnigroff] master branch, is the version from "nroff -v" always the same as from "groff -v"? ___

[bug #62776] [troff] want "style" warning category for self-deceptive inputs

Follow-up Comment #17, bug #62776 (project groff): Following up on comment #4... * Warn when `\\` encountered in interpretation mode. The user wants `\e` or (if the escape character is the default) `\[rs]` instead. * Warn when `\.` encountered in interpretation mode. _