[bug #63590] [pdfmark] some spelling mistakes found with "codespell"

Update of bug #63590 (group groff): Status:None => Invalid Assigned to:None => gbranden Open/Closed:Open => Closed ___ Follow-up Comment

[bug #66447] [troff] page break caused by .ne behaves differently from .bp

Follow-up Comment #7, bug #66447 (group groff): At 2024-11-15T18:38:59-0500, anonymous wrote: > Follow-up Comment #6, bug #66447 (group groff): > [comment #5 comment #5:] >> I know that for other requests, I sometimes want to "schedule" >> something to take place when the next break happens withou

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

Follow-up Comment #9, bug #66438 (group groff): [comment #8 comment #8:] > @Branden: Out of curiosity and eagerness to learn: Why do you wrap the range > expressions into bracket expressions, like this? To quote the brackets the shell command needs to see. > [[0-9]][[0-9]]*\.[[0-9]][[0-9]]*\.[

[bug #58948] [me] support automatic bookmarks/tags

Update of bug #58948 (group groff): Summary: [me] adapt to use the facilities of pdfmark => [me] support automatic bookmarks/tags ___ Follow-up Comment #2: We don't need to use pdfmark.tmac, but it would still be worthwhil

[bug #58946] [ms] support automatic bookmarks/tags

Update of bug #58946 (group groff): Summary: [ms] adapt to use the facilities of pdfmark => [ms] support automatic bookmarks/tags ___ Follow-up Comment #16: We don't need to use pdfmark.tmac, but it would still be worthwhi

[bug #58947] [mm] support automatic bookmarks/tags

Update of bug #58947 (group groff): Summary: [mm] adapt to use the facilities of pdfmark => [mm] support automatic bookmarks/tags ___ Follow-up Comment #2: We don't need to use pdfmark.tmac, but it would still be worthwhil

[bug #66447] [troff] page break caused by .ne behaves differently from .bp

Follow-up Comment #4, bug #66447 (group groff): [comment #2 comment #2:] > > [comment #1 comment #1:] >> cc: onf disroot org > > Savannah doesn't interpret this, but I tried to, and updated the ticket's CC > list. I know it doesn't; I don't have permission to do it without an account. I hoped a

[bug #66447] [troff] page break caused by .ne behaves differently from .bp

Follow-up Comment #6, bug #66447 (group groff): [comment #5 comment #5:] > I know that for other requests, I sometimes want to "schedule" something > to take place when the next break happens without actually _causing_ a > break. I haven't thought carefully through enough scenarios to decide > t

[bug #66447] page break caused by .ne behaves differently from .bp

Follow-up Comment #1, bug #66447 (group groff): cc: onf disroot org ___ Reply to this item at: ___ Message sent via Savannah https://savannah.gnu.org/

[bug #66447] page break caused by .ne behaves differently from .bp

URL: Summary: page break caused by .ne behaves differently from .bp Group: GNU roff Submitter: None Submitted: Fri 15 Nov 2024 05:10:58 PM UTC Category: Core S

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

Update of bug #65354 (group groff): Status: Confirmed => Invalid Assigned to:None => gbranden Open/Closed:Open => Closed ___ Follow-up Comment

[bug #66447] [troff] page break caused by .ne behaves differently from .bp

Follow-up Comment #5, bug #66447 (group groff): At 2024-11-15T17:55:15-0500, anonymous wrote: >> This doesn't change the output, because commanding a break >> conditional on `ne`eded vertical space does not establish a vertical >> position trap. That's interesting. I'd never considered that >> s

[bug #65117] [pdfmark] premature page break in "pdfmark.ms" output with page size A4

Update of bug #65117 (group groff): Assigned to:None => gbranden ___ Reply to this item at: ___ Message sent via Savann

[bug #63827] withdraw contrib/pdfmark

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

[bug #60927] improve pdfmark documentation, including pdfroff(1)

Update of bug #60927 (group groff): Status: In Progress => Invalid Assigned to: keithmarshall => gbranden Open/Closed:Open => Closed ___ Follow-up Comment

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

Follow-up Comment #8, bug #66438 (group groff): @Branden: Out of curiosity and eagerness to learn: Why do you wrap the range expressions into bracket expressions, like this? [[0-9]][[0-9]]*\.[[0-9]][[0-9]]*\.[[0-9]][[0-9]]* It seems a bit redundant to me, as this shorter version also matches f

[bug #66447] [troff] page break caused by .ne behaves differently from .bp

Follow-up Comment #2, bug #66447 (group groff): [comment #1 comment #1:] > cc: onf disroot org Savannah doesn't interpret this, but I tried to, and updated the ticket's CC list. ___ Reply to this item at:

[bug #66447] [troff] page break caused by .ne behaves differently from .bp

Follow-up Comment #3, bug #66447 (group groff): [comment #0 original submission:] > I have turned off hyphenating at the end of the > page, I don't see where. You have this: .hy 4 ...bit 1 is not set in this integer, so hyphenation is not suppressed prior to a vertical position trap. You p

[bug #66447] [troff] page break caused by .ne behaves differently from .bp

Update of bug #66447 (group groff): Status:None => Need Info Summary: page break caused by .ne behaves differently from .bp => [troff] page break caused by .ne behaves differently from .bp

[bug #66447] [troff] page break caused by .ne behaves differently from .bp

Follow-up Comment #8, bug #66447 (group groff): [comment #7 comment #7:] > At 2024-11-15T18:38:59-0500, anonymous wrote: >> Follow-up Comment #6, bug #66447 (group groff): >> [comment #5 comment #5:] >>> I know that for other requests, I sometimes want to "schedule" >>> something to take place wh

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

Follow-up Comment #10, bug #66438 (group groff): > To quote the brackets the shell command needs to see. Thank you for clearing that up to me! I did not think about the m4 context, _and_ I did not think of `[`and `]` being m4's quote characters. > I don't remember if POSIX character classes are