Re: [bug #59573] typesetting.mom: traps are not initialised (set, planted)

The commit for this is pushed! :) At 2020-12-05T22:33:25-0500, T. Kurt Bond wrote: > I'll note that Heirloom troff does not issue any warnings. I don't know you if meant that just with respect to the instant issue, but it's a general truth--the whole concept of warnings on roff input is a

[bug #59573] typesetting.mom: traps are not initialised (set, planted)

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

Re: [bug #59573] typesetting.mom: traps are not initialised (set, planted)

On Sat, 05 Dec 2020 13:35:09 -0500, Peter Schaffter wrote: > On Sun, Dec 06, 2020, G. Branden Robinson wrote: > > 3. Downgrade the error to a warning. > > This seems reasonable, given the current nop behaviour, which > groffers expect. It is useful for debugging to know a trap hasn't > been

Re: [bug #59573] typesetting.mom: traps are not initialised (set, planted)

On Sun, Dec 06, 2020, G. Branden Robinson wrote: > Hi Peter! > > Thanks for the swift follow-up! > > At 2020-12-05T13:35:09-0500, Peter Schaffter wrote: > > On Sun, Dec 06, 2020, G. Branden Robinson wrote: > > > 1. Revert the change, possibly telling users in the manual how > > > write their

Re: [bug #59573] typesetting.mom: traps are not initialised (set, planted)

Hi Peter! Thanks for the swift follow-up! At 2020-12-05T13:35:09-0500, Peter Schaffter wrote: > On Sun, Dec 06, 2020, G. Branden Robinson wrote: > > 1. Revert the change, possibly telling users in the manual how > > write their own validity-testing wrapper for .ch. > > What would such a

[bug #59573] typesetting.mom: traps are not initialised (set, planted)

Update of bug #59573 (project groff): Severity: 3 - Normal => 5 - Blocker ___ Follow-up Comment #4: Setting as blocker because a decision needs to be taken before release.

Re: [bug #59573] typesetting.mom: traps are not initialised (set, planted)

On Sun, Dec 06, 2020, G. Branden Robinson wrote: > [redirecting to groff@ for discussion] > > Background: In https://savannah.gnu.org/bugs/index.php?59573, Bjarni > pointed out that a recent change I made caused some diagnostics to > appear. > > troff:

[bug #59573] typesetting.mom: traps are not initialised (set, planted)

Update of bug #59573 (project groff): Status: Confirmed => Need Info Assigned to:PTPi => gbranden ___ Follow-up Comment #3: Mailing list

Re: [bug #59573] typesetting.mom: traps are not initialised (set, planted)

[redirecting to groff@ for discussion] Background: In https://savannah.gnu.org/bugs/index.php?59573, Bjarni pointed out that a recent change I made caused some diagnostics to appear. > GROFFcontrib/mom/examples/typesetting.pdf > troff: ../contrib/mom/examples/typesetting.mom:638: error:

[bug #59573] typesetting.mom: traps are not initialised (set, planted)

Follow-up Comment #2, bug #59573 (project groff): Until now, the exhibited behaviour of groff, if not the intended behaviour, was to ignore .ch requests for non-existent traps. The file typesetting.mom demonstrates bare-metal typesetting, so the FOOTER and FN_OVERFLOW traps, which are only used

[bug #59573] typesetting.mom: traps are not initialised (set, planted)

Update of bug #59573 (project groff): Category:Core => Macro - mom Status:None => Confirmed Assigned to:None => PTPi

[bug #59573] typesetting.mom: traps are not initialised (set, planted)

URL: Summary: typesetting.mom: traps are not initialised (set, planted) Project: GNU troff Submitted by: bjarniig Submitted on: Mon 30 Nov 2020 01:06:18 AM UTC Category: Core