[bug #66673] [troff] fix for bug #66434 absorbs pre-comment spaces into request argument

Update of bug #66673 (group groff): Status:None => Confirmed Assigned to:None => gbranden Summary: Fix for bug #66434 breaks a common legacy syntax => [troff] fix for bug #66434 absorbs pre-comment spaces into

[bug #66673] [troff] fix for bug #66434 absorbs pre-comment spaces into request argument

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

[bug #65099] 1.24.0 release goals

Update of bug #65099 (group groff): Depends on: => bugs #66673 ___ Reply to this item at: ___ Message sent via Sav

[bug #57538] .ne is off by one in some macro packages even when using no other facilities of that package

Follow-up Comment #24, bug #57538 (group groff): Side note: The original test input, from comment #0, is no longer relevant to this bug; as comment #22 says, everything before comment #13 here can pretty much be ignored now. But this input now fails in a new (as of two months ago) way, which is

[bug #66673] Fix for bug #66434 breaks a common legacy syntax

URL: Summary: Fix for bug #66434 breaks a common legacy syntax Group: GNU roff Submitter: barx Submitted: Thu 16 Jan 2025 08:46:46 AM CST Category: Core Severi

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

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

[bug #66673] [troff] fix for bug #66434 absorbs pre-comment spaces into request argument

Follow-up Comment #2, bug #66673 (group groff): [comment #1 comment #1:] > We don't know that a run of _n_ spaces is "trailing" until we > hit a token that _isn't_ a space, Without looking at the code, I can't say for sure, but conceptually this doesn't seem like as onerous as that: you don't act

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

Update of bug #66675 (group groff): Status:None => Confirmed Assigned to:None => gbranden Summary: valid .char definition provoking erroneous error => [troff] valid .char definition starting with `\[u` provokes

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

Follow-up Comment #4, bug #66675 (group groff): At 2025-01-16T21:05:03-0500, Dave wrote: > Follow-up Comment #2, bug #66675 (group groff): > > [comment #1 comment #1:] >> \[u...] means an unicode character. > > It was permitted to mean other things for the past at least 20 years > and I bet a lot

[bug #66675] valid .char definition provoking erroneous error

URL: Summary: valid .char definition provoking erroneous error Group: GNU roff Submitter: barx Submitted: Thu 16 Jan 2025 03:54:17 PM CST Category: Core Severi

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

Follow-up Comment #5, bug #66434 (group groff): Bug #66673 further refined the documentation associated with this change. ___ Reply to this item at: ___

[bug #66675] valid .char definition provoking erroneous error

Follow-up Comment #2, bug #66675 (group groff): [comment #1 comment #1:] > \[u...] means an unicode character. It was permitted to mean other things for the past at least 20 years and I bet a lot longer. $ nroff --version GNU nroff (groff) version 1.19.2 $ printf '.char \[unhappy] :-(\nI feel \[

[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 ___ Follow-up Comment #19: commit f2f0b8e1f7e1edbf63239107bdcce65a8fdeca24 Author:

[bug #66673] [troff] fix for bug #66434 absorbs pre-comment spaces into request argument

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

[bug #66675] valid .char definition provoking erroneous error

Follow-up Comment #1, bug #66675 (group groff): \[u...] means an unicode character. Use 'Unhappy' instead. ___ Reply to this item at: ___ Message sent

[bug #66673] [troff] fix for bug #66434 absorbs pre-comment spaces into request argument

Follow-up Comment #5, bug #66673 (group groff): [comment #3 comment #3:] >> Alternately, you could skip the flag and always ax the trailing >> spaces. > > Not now. Sorry, I was unclear here. By "you" I meant "the function that opens a file," not "read_string()". But that's moot now. Thanks fo

[bug #66673] [troff] fix for bug #66434 absorbs pre-comment spaces into request argument

Follow-up Comment #3, bug #66673 (group groff): Hi Dave, I'll rearrange your comment a bit for my reply. At 2025-01-16T14:35:12-0500, Dave wrote: > Follow-up Comment #2, bug #66673 (group groff): > > Alternately, you could skip the flag and always ax the trailing > spaces. Not now. The way I c

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

Follow-up Comment #3, bug #66675 (group groff): At 2025-01-16T20:03:05-0500, Bjarni Ingi Gislason wrote: > Follow-up Comment #1, bug #66675 (group groff): > > \[u...] means an unicode character. No, it's only a Unicode special character escape sequence if it's valid as such--otherwise it's an ord