[bug #66686] [troff] `\w` escape sequence rejecting delimiters roffs have accepted for decades

Follow-up Comment #6, bug #66686 (group groff): At 2025-01-29T03:38:30-0500, Dave wrote: > Follow-up Comment #5, bug #66686 (group groff): > > This fix did the trick. Thanks! > > My only quibble (and you knew I'd have one) is with the wording of the > warning. ;-) > $ echo "Length of 'abc': \w

[bug #66686] [troff] `\w` escape sequence rejecting delimiters roffs have accepted for decades

Follow-up Comment #5, bug #66686 (group groff): This fix did the trick. Thanks! My only quibble (and you knew I'd have one) is with the wording of the warning. $ echo "Length of 'abc': \w+abc+u" | groff -Tascii -ww | cat -s troff::1: warning: interpreting character '+' as an escape sequence del

[bug #66016] [troff] document AT&T and GNU differences in `hw` exception word handling

Follow-up Comment #2, bug #66016 (group groff): [comment #0 original submission:] > .hw word > Specify hyphenation points in words with embedded minus signs. > Versions of a word with a terminal s are implied; i.e., dig-it > implies dig-its. Fun fact about this: the additional s is implied even

[bug #66731] [PATCH] update Gnulib module names

Follow-up Comment #1, bug #66731 (group groff): Thanks for posting. I prefer email to the bug tracker. But groff's preference is obviously different. :) ___ Reply to this item at:

[bug #66732] Words not hyphenated in non-default environment

Update of bug #66732 (group groff): Status:None => Duplicate Assigned to:None => barx Open/Closed:Open => Closed ___ Follow-up Comment #

[bug #66392] full-service macro packages lose track of hyphenation mode in environments other than 0

Update of bug #66392 (group groff): Category:Macro package me => Macro package - others/general Summary: [me] loses track of hyphenation mode in environment 1 => full-service macro packages lose track of hyphenation mode in environments other than 0 __

[bug #66673] [troff] document that more requests absorb pre-comment spaces into their argument

Update of bug #66673 (group groff): Summary: [troff] fix for bug #66434 absorbs pre-comment spaces into request argument => [troff] document that more requests absorb pre-comment spaces into their argument ___ Reply to thi

[bug #66392] [me] loses track of hyphenation mode in environment 1

Update of bug #66392 (group groff): Status: Invalid => Confirmed Open/Closed: Closed => Open ___ Follow-up Comment #6: Reopening pending an answer to the last question in comm

[bug #66392] [me] loses track of hyphenation mode in environment 1

Follow-up Comment #7, bug #66392 (group groff): Yes, _ms_ and _me_ need to be updated to copy environment `0` to the ones they create, if/where this isn't already done. ___ Reply to this item at:

[bug #66731] [PATCH] update Gnulib module names

Update of bug #66731 (group groff): Status:None => Confirmed Summary: [PATCH] Update Gnulib module names. => [PATCH] update Gnulib module names ___ Reply to this item at:

[bug #66392] [me] loses track of hyphenation mode in environment 1

Follow-up Comment #5, bug #66392 (group groff): [comment #4 comment #4:] > So lines hyphenate and break differently with the fix to bug #66387 > applied--not globally across the document, but in certain environments. > > Does this break backward compatibility? [...] > With GNU _troff_, the answer

[bug #66732] Words not hyphenated in non-default environment

Follow-up Comment #2, bug #66732 (group groff): [comment #1 comment #1:] > This _may_ be due to a deliberate change. But I'm going to hide the > salami and ask you to run the `pev` request in your failing environment Ah. $ cat 66732 .ll 20n .hy 4 My text contains the word antidisestablishmentar