[bug #66350] [troff] warnings in "mac" category can be misleading

Update of bug #66350 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 ___ Follow-up Comment #3:

[bug #66432] [troff] want `device` request to support composite special character escape sequences

Update of bug #66432 (group groff): Status:None => Postponed ___ Follow-up Comment #1: Kicking out beyond _groff_ 1.24. ___ Reply to this item

[bug #66438] configure fails on macOS since 180d665d19

Follow-up Comment #5, bug #66438 (group groff): Great! I just checked: matches again. Thank you very much! ___ Reply to this item at: ___ Message sent v

[bug #66438] configure fails on macOS since 180d665d19

Update of bug #66438 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 ___ Follow-up Comment #4:

[bug #66419] [libgroff] seems like fix for bug 61424 was too aggressive

Update of bug #66419 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 ___ Follow-up Comment #16

[bug #66027] [soelim] stop requiring spaces to be backslash-escaped, and strip leading double quote

Update of bug #66027 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 ___ Follow-up Comment #3:

[bug #66434] [troff] want `so` and related requests to accept file names with embedded spaces

Update of bug #66434 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 ___ Follow-up Comment #4:

[bug #63074] [troff] support expression of arbitrary byte sequences in device control commands

Update of bug #63074 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 ___ Follow-up Comment #43

[bug #65077] [ms] unexpected suppression of `sp` effect after `DE` call

Follow-up Comment #8, bug #65077 (group groff): Sure, but any request for a behavior change carries some element of advocacy. It's just that some things being advocated require less justification than others. ("When I set the font size to 12 points, groff dumps core." "OK, but why do you think t

[bug #66438] configure fails on macOS since 180d665d19

Follow-up Comment #6, bug #66438 (group groff): According to the documentation for GNU expr, the : operator uses "a (basic, a la GNU 'grep') regular expression"; a couple paragraphs later, it clarifies: In the regular expression, '\+', '\?', and '\|' are operators which respectively match o

[bug #65788] [gropdf] "warning: PDF Dict Key 'User' does not start with '/'"

Update of bug #65788 (group groff): Summary: gropdf: warning: PDF Dict Key 'User' does not start with '/' => [gropdf] "warning: PDF Dict Key 'User' does not start with '/'" ___ Reply to this item at:

[bug #66443] nested-string syntax either buggy or underdocumented

URL: Summary: nested-string syntax either buggy or underdocumented Group: GNU roff Submitter: barx Submitted: Thu 14 Nov 2024 08:00:29 PM CST Category: Core Se

[bug #66410] [mdoc] warning of .Lb usage without library definition excessive

Update of bug #66410 (group groff): Summary: mdoc: warning of .Lb usage without library definition excessive => [mdoc] warning of .Lb usage without library definition excessive ___ Reply to this item at:

[bug #65829] [troff] want way to translate a character to \~

Update of bug #65829 (group groff): Status:None => Postponed ___ Follow-up Comment #1: Post-1.24. ___ Reply to this item at:

[bug #65108] [troff] support construction of general file name request arguments

Update of bug #65108 (group groff): Status:None => Postponed ___ Follow-up Comment #19: Post-1.24. ___ Reply to this item at:

[bug #66348] [troff] support neatroff's `.%` register for page sequence number

Update of bug #66348 (group groff): Status:None => Postponed ___ Follow-up Comment #1: Post-1.24. ___ Reply to this item at:

[bug #66442] [ms] Change due to #62688 wrecks vertical spacing model

URL: Summary: [ms] Change due to #62688 wrecks vertical spacing model Group: GNU roff Submitter: keithmarshall Submitted: Thu 14 Nov 2024 06:27:52 PM UTC Category: Macro packa

[bug #65558] [UPGRADE] [troff] improve paragraph formatting within line-at-a-time processing

Update of bug #65558 (group groff): Status:None => Postponed Summary: [UPGRADE] improve paragraph formatting within groff's line-at-a-time processing => [UPGRADE] [troff] improve paragraph formatting within line-at-a-time processing _

[bug #64966] [troff] make the underline font environment-specific

Update of bug #64966 (group groff): Status:None => Postponed ___ Follow-up Comment #1: Post-1.24. ___ Reply to this item at:

[bug #66442] [ms] Change due to #62688 wrecks vertical spacing model

Follow-up Comment #2, bug #66442 (group groff): [comment #0 original submission:] > While I agree with the premise that accumulation of display space is > undesirable, the solution for that problem, The most generous concession I've ever heard you make on any subject! Bravo! Unfortunately you t

[bug #63074] support expression of arbitrary byte sequences in device extension commands

Update of bug #63074 (group groff): Summary: support expression of arbitrary byte sequences in device control commands => support expression of arbitrary byte sequences in device extension commands ___ Follow-up Comment #45

[bug #63074] support expression of arbitrary byte sequences in device control commands

Update of bug #63074 (group groff): Summary: [troff] support expression of arbitrary byte sequences in device control commands => support expression of arbitrary byte sequences in device control commands ___ Follow-up Comme

[bug #66438] configure fails on macOS since 180d665d19

Follow-up Comment #7, bug #66438 (group groff): [comment #6 comment #6:] > According to the documentation for GNU expr, the : operator uses "a (basic, a > la GNU 'grep') regular expression"; a couple paragraphs later, it clarifies: > In the regular expression, '\+', '\?', and '\|' are operators w

[bug #64478] [troff] want mechanism to clear hyphenation patterns defined with .hw

Update of bug #64478 (group groff): Status:None => Postponed ___ Follow-up Comment #1: Post-1.24. ___ Reply to this item at:

[bug #65077] [ms] unexpected suppression of `sp` effect after `DE` call

Follow-up Comment #4, bug #65077 (group groff): Rejected? Why? This is a critical regression from groff-1.22.4, which I discovered only this week, after removing a modified 1.22.4 copy of s.tmac from my groff-pdfmark working tree; this regression _seriously_ messes up the front-matter layout of p

[bug #65077] [ms] unexpected suppression of `sp` effect after `DE` call

Update of bug #65077 (group groff): Status:Rejected => Need Info Assigned to:barx => None Open/Closed: Closed => Open ___ Follow-up Comment #5:

[bug #66442] [ms] Change due to #62688 wrecks vertical spacing model

Update of bug #66442 (group groff): Status:None => Duplicate Assigned to:None => gbranden Open/Closed:Open => Closed ___ Follow-up Comme

[bug #63827] withdraw contrib/pdfmark

Update of bug #63827 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Reply to this item at: __

[bug #63827] withdraw contrib/pdfmark

Follow-up Comment #17, bug #63827 (group groff): [comment #15 comment #15:] > A little detangling from _mom_(7) will be necessary. I retract that; _mom_ can still use Keith's _pdfmark_ no matter where it comes from, and removing contrib/pdfmark causes no _mom_ test failures, so I see no reason t

[bug #64484] [troff] `.device` and `\X` should have a policy for non-special character node handling

Update of bug #64484 (group groff): Status:None => Need Info ___ Follow-up Comment #28: Putting in "Need info" state since a decision is required; Deri and I have different opinions; he leans in a DWIM

[bug #64484] [troff] `.device` and `\X` should have a policy for non-special character node handling

Update of bug #64484 (group groff): Summary: [troff] .device should encode special characters in `\[u]` form => [troff] `.device` and `\X` should have a policy for non-special character node handling ___ Follow-up Comme

[bug #65344] [troff] want a more limited no-space mode

Update of bug #65344 (group groff): Status:None => Postponed Summary: want a more limited no-space mode => [troff] want a more limited no-space mode ___ Follow-up Comment #1: Post-1.24

[bug #65354] [pdfmark] using -mspdf with -Tpdf signals error: pdfhref:init: unknown feature '-PT'

Follow-up Comment #3, bug #65354 (group groff): FWIW, my [https://osdn.net/users/keith/pf/groff-pdfmark/wiki/FrontPage groff-pdfmark] implementation has left your contrib/pdfmark a _long_ way behind, (and hence, effectively obsolete). Furthermore, _my_ spdf.tmac _explicitly_ loads _both_ s.tmac, a

[bug #65954] [troff] next-generation alignment and adjustment control

Update of bug #65954 (group groff): Status:None => Postponed ___ Reply to this item at: ___ Message sent via Savan

[bug #65077] [ms] unexpected suppression of `sp` effect after `DE` call

Follow-up Comment #6, bug #65077 (group groff): A sentence in bug #66442 summarizes the issue more succinctly, I think, than anything here: "activation of no-space mode, after output of \n[DD] space is *not* the solution to bug #62688, because it inhibits *all* forms of explicitly user-specified

[bug #65077] [ms] unexpected suppression of `sp` effect after `DE` call

Follow-up Comment #7, bug #65077 (group groff): [comment #6 comment #6:] > A sentence in bug #66442 summarizes the issue more succinctly, I think, than > anything here: > > "activation of no-space mode, after output of \n[DD] space is *not* the > solution to bug #62688, because it inhibits *all*

[bug #66438] configure fails on macOS since 180d665d19

Follow-up Comment #3, bug #66438 (group groff): At 2024-11-14T06:28:42-0500, Sven Schober wrote: > Follow-up Comment #2, bug #66438 (group groff): >> Unfortunately, the `\{1,\}` solution you propose is also not a POSIX >> BRE. > > Hmm, okay, I did not read the POSIX spec/standard (yet?). Issue 8,

[bug #66438] configure fails on macOS since 180d665d19

Update of bug #66438 (group groff): Status: Confirmed => In Progress ___ Reply to this item at: ___ Message sent via Sav

[bug #63074] [troff] support expression of arbitrary byte sequences in device control commands

Follow-up Comment #42, bug #63074 (group groff): Here's my attempt to explain this new feature in the "NEWS" file. * GNU troff now performs some limited processing/transformation of the argument to the `\X` escape sequence and its counterpart `device` request, to address the requirem

[bug #66438] configure fails on macOS since 180d665d19

Follow-up Comment #2, bug #66438 (group groff): > Unfortunately, the `\{1,\}` solution you propose is also not a POSIX BRE. Hmm, okay, I did not read the POSIX spec/standard (yet?). But this whole basic vs extended RE business is really unfortunate in my opinion. I always struggle, everytime I w