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

Follow-up Comment #1, bug #66434 (group groff): As discussed in bug #65108 (of which the current bug is a special case), this change, as presented, will make the .so request require a different syntax when soelim is used than when it isn't. A way around this discussed in 65108 is removing the bac

[bug #64450] [nroff] reclaim -e, -s flags for preprocessors?

Follow-up Comment #5, bug #64450 (group groff): [comment #4 comment #4:] > It's in the commit's diff. Oh. Yes, I do remember (now) how scrollbars work... I observe that the added comment section lists -p as one of the options nroff doesn't support, despite nroff supporting this option since at

[bug #65099] 1.24.0 release goals

Update of bug #65099 (group groff): Depends on: => bugs #66027 ___ 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 #41, bug #63074 (group groff): Hi Deri, At 2024-11-12T13:47:33-0500, Deri James wrote: > Follow-up Comment #40, bug #63074 (group groff): > > [comment #38 comment #38:] >> One could envision three levels of support for encoding arbitrary >> characters. >> >> 1. By Unicode code

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

Follow-up Comment #1, bug #66027 (group groff): This is a one-liner. diff --git a/src/preproc/soelim/soelim.cpp b/src/preproc/soelim/soelim.cpp index e10447d06..18f37870f 100644 --- a/src/preproc/soelim/soelim.cpp +++ b/src/preproc/soelim/soelim.cpp @@ -141,7 +141,7 @@ void do_so(const char *lin

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

Follow-up Comment #3, bug #66434 (group groff): [comment #2 comment #2:] > In progress as we speak... Oh. I missed bug #66027 altogether. Today is my day for overlooking what's in plain sight. Thanks for removing my blinders. ___ Reply

[bug #64450] [nroff] reclaim -e, -s flags for preprocessors?

Follow-up Comment #4, bug #64450 (group groff): At 2024-11-12T11:37:27-0500, Dave wrote: > Follow-up Comment #3, bug #64450 (group groff): > > [comment #2 comment #2:] >> I very recently decided against that. >> >> https://git.savannah.gnu.org/cgit/groff.git/commit/?id=78394f9f5bbf22f7505c751c122f

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

Follow-up Comment #18, bug #65108 (group groff): [comment #17 comment #17:] > Which emails notifications I receive seems to be pretty erratic. Savannah seems to be under a lot of churn lately--which is overall a good thing, as useful features are being added. But yeah, I did notice http://savann

[bug #64450] [nroff] reclaim -e, -s flags for preprocessors?

Follow-up Comment #3, bug #64450 (group groff): [comment #2 comment #2:] > I very recently decided against that. > > https://git.savannah.gnu.org/cgit/groff.git/commit/?id=78394f9f5bbf22f7505c751c122f5b9c5f174073 That commit adds some flags to nroff, but is silent on why others were decided agai

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

Follow-up Comment #2, bug #66434 (group groff): [comment #1 comment #1:] > A way around this discussed in 65108 is removing the backslash requirement > from soelim. As you observed, "Since backslash-space is apparently a GNU > extension in the first place, we might consider dropping it." In prog

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

Follow-up Comment #40, bug #63074 (group groff): [comment #38 comment #38:] > One could envision three levels of support for encoding arbitrary > characters. > > 1. By Unicode code point. Reusing _groff_'s own syntax for Unicode special > character escape sequences was irresistibly tempting, so

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

Follow-up Comment #17, bug #65108 (group groff): [comment #16 comment #16:] > [comment #8 comment #8:] >> A. what to do about `\ ` in GNU _soelim_ and _troff_. > > The soelim part is now covered by bug #66027. ...and the _troff_ part by bug #66434, where the answer is basically "nothing"; I re

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

Follow-up Comment #16, bug #65108 (group groff): [comment #8 comment #8:] > A. what to do about `\ ` in GNU _soelim_ and _troff_. The soelim part is now covered by bug #66027. (This bug was modified to depend on 66027 the same day comment #8 and comment #9 were posted, but if there was an email

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

Follow-up Comment #2, bug #66027 (group groff): Er, it's a one liner to handle the unescaped space. ___ Reply to this item at: ___ Message sent via Sava

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

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

[bug #65099] 1.24.0 release goals

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

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

URL: Summary: [troff] want `so` and related requests to accept file names with embedded spaces Group: GNU roff Submitter: gbranden Submitted: Tue 12 Nov 2024 03:22:01 PM UTC C