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

2023-04-26 Thread Dave
Follow-up Comment #5, bug #62776 (project groff): [comment #4 comment #4:] > 2. Invoking a non-breaking request with the no-break control > character; the user will think they're saying something > meaningful, but they are not. One may not be saying something meaningful to groff, but may be to a

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

2023-04-26 Thread G. Branden Robinson
Follow-up Comment #6, bug #62776 (project groff): [comment #5 comment #5:] > One may not be saying something meaningful to groff, but may be to a human reader. For example, if a user-defined macro should not cause a break, and that macro invokes five requests, two of which cause a break, then as

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

2023-04-26 Thread Dave
Follow-up Comment #7, bug #62776 (project groff): [comment #6 comment #6:] > the technique you describe, which I have not seen in the wild, I haven't either, just thinking out loud (or the virtual version thereof). ___ Reply to this item

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

2023-04-26 Thread Alejandro Colomar
Follow-up Comment #8, bug #62776 (project groff): [comment #6 comment #6:] > Also I think the technique you describe, which I have not seen in the wild, might be too clever by half. Better to say in English in a comment, "This macro is intended to cause no breaks.", no? I tend to prefer actual

[bug #64114] [pdfpic] when falling back to EPS, should create file in temporary directory, but doesn't

2023-04-26 Thread G. Branden Robinson
URL: Summary: [pdfpic] when falling back to EPS, should create file in temporary directory, but doesn't Group: GNU roff Submitter: gbranden Submitted: Wed 26 Apr 2023 10:51:18 AM UTC

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

2023-04-26 Thread Dave
Follow-up Comment #9, bug #62776 (project groff): comment #8 comment #8:] > Disabling a warning if you don't care is easy. I would love for that to be true of groff warnings. Unfortunately, you can only enable and disable warnings by category, the existing categories range in scope from ridiculo

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

2023-04-26 Thread Alejandro Colomar
Follow-up Comment #10, bug #62776 (project groff): [comment #9 comment #9:] > comment #8 comment #8:] > > Disabling a warning if you don't care is easy. > > I would love for that to be true of groff warnings. Unfortunately, you can only enable and disable warnings by category, the existing cate

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

2023-04-26 Thread Dave
Follow-up Comment #11, bug #62776 (project groff): That exceeds the bounds of what I would deem "easy." :) A groff warning category can be disabled from within the document source with the .warn request. Your method not only takes control away from the document itself, it also realistically requ