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

2025-02-03 Thread Dave
Follow-up Comment #24, bug #66392 (group groff): [comment #23 comment #23:] > I'm trying to get 1.24.0 toward a release and I am not anxious to > mediate a dispute between advocates of these three positions, In terms of what's least disruptive for an imminent release, perhaps simplest is to roll

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

2025-02-03 Thread Peter Schaffter
Follow-up Comment #27, bug #66392 (group groff): [comment #26 comment #26:] >> I'm in complete agreement with Dave. Roll back the change and have a >> good chinwag about environment switching after 1.24. The minutiae of >> Branden's comments are veering dangerously close to angels on the head

[bug #66675] [troff] valid .char definition starting with `\[u` provokes erroneous error

2025-02-03 Thread Dave
Follow-up Comment #11, bug #66675 (group groff): [comment #9 comment #9:] > Not at all. I stand by comment #4; you identified > a flaw in code I wrote, and I aim to fix it. Sorry, I should have given more context for my comment #8. In particular, nothing in comment #4 gave me pause. What did,

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

2025-02-03 Thread G. Branden Robinson
Follow-up Comment #23, bug #66392 (group groff): At 2025-02-03T06:29:31-0500, Deri James wrote: > Follow-up Comment #22, bug #66392 (group groff): >> I think a lot of people assume that when they create a new >> environment, it's a copy of environment 0 already. But it isn't. > > Given that you b

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

2025-02-03 Thread Deri James
Follow-up Comment #22, bug #66392 (group groff): > I think a lot of people assume that when they create a new environment, it's a copy of environment 0 already. But it isn't. Given that you believe this (and I think you are spot on) I wondered why you didn't "solve" the inconsistency by ensur

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

2025-02-03 Thread G. Branden Robinson
Follow-up Comment #26, bug #66392 (group groff): At 2025-02-03T11:24:56-0500, Dave wrote: > Follow-up Comment #24, bug #66392 (group groff): > > [comment #23 comment #23:] >> I'm trying to get 1.24.0 toward a release and I am not anxious to >> mediate a dispute between advocates of these three pos

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

2025-02-03 Thread Peter Schaffter
Follow-up Comment #25, bug #66392 (group groff): [comment #24 comment #24:] > In terms of what's least disruptive for an imminent release, perhaps simplest > is to roll back the change making hyphenation language per-environment. I'm in complete agreement with Dave. Roll back the change and hav