Re: warning on mid-input line sentence endings (was: Warn on semantic newlines)

2022-10-23 Thread G. Branden Robinson
At 2022-07-17T09:18:28-0500, Dave Kemper wrote: > On 7/16/22, G. Branden Robinson wrote: > > I think a new, writable troff register would be a better way to > > manipulate this feature--which is basically a style diagnostic--than > > a warning category. > > This suggests that one day there might

Re: What to call \&, redux (was: warning on mid-input line sentence endings)

2022-07-26 Thread Dave Kemper
In an attempt to consolidate discussion about this that has heretofore ranged far and wide, I've opened http://savannah.gnu.org/bugs/?62816. It links to all previous discussions on the topic I could find; please comment there if I've missed any, or if you have further thoughts that aren't covered b

Re: warning on mid-input line sentence endings (was: Warn on semantic newlines)

2022-07-23 Thread Ralph Corderoy
Hi, Dave Kemper wrote: > Luckily, "newsentence" is shorter. In case they trigger other suggestions: - want line end - two sentences - sentences - trailing sentence - trailing words - trailing characters - end-of-sentence noise - EoS noise -- Cheers, Ralph.

Re: warning on mid-input line sentence endings (was: Warn on semantic newlines)

2022-07-22 Thread Dave Kemper
On 7/17/22, G. Branden Robinson wrote: > I'm having trouble thinking of single other example that needs > to operate at the level of the formatter as this one does. Hmm... does the USER care what level it's operating at? Should the user interface for this low-level diagnostic look basically like

Re: warning on mid-input line sentence endings (was: Warn on semantic newlines)

2022-07-21 Thread Bjarni Ingi Gislason
The simplest word I have thought of is "singlespace".

What to call \&, redux (was: warning on mid-input line sentence endings)

2022-07-17 Thread G. Branden Robinson
Hi Peter! At 2022-07-17T11:47:59-0400, Peter Schaffter wrote: > > Note the omission of the ineffable \& escape sequence after one of > > the initials. > > Appreciation for the exquisite choice of adjective. :) I've adopted it in emails since I started to get yelled at every time I used my own no

Re: warning on mid-input line sentence endings

2022-07-17 Thread G. Branden Robinson
Hi Doug, At 2022-07-17T13:31:13-0400, Douglas McIlroy wrote: > >> In regard to turning the warning on or off, the warning should not > >> be given when sentence spacing is set to 0 > > > I'm not sure I agree > > I withdraw the suggestion. Since the default .ss 12 12 has the same > effect at a mi

Re: warning on mid-input line sentence endings

2022-07-17 Thread josh
Hi Branden and Dave, > The devilish problem is that I don't know what to put > _before_ the period in the register name for _this_ > issue. > I'd like to hear suggestions. Adding on my suggestion as an innocent bystander. The style problem as I understand it is “there are multiple sentences per

Re: warning on mid-input line sentence endings

2022-07-17 Thread Douglas McIlroy
>> In regard to turning the warning on or off, the warning should not be >> given when sentence spacing is set to 0 > I'm not sure I agree I withdraw the suggestion. Since the default .ss 12 12 has the same effect at a mid-line "sentence space" as copying the double space, I had not realized that

Re: warning on mid-input line sentence endings

2022-07-17 Thread Peter Schaffter
Branden -- > Note the omission of the ineffable \& escape sequence after one of > the initials. Appreciation for the exquisite choice of adjective. :) O.T., I know, but have we reached a consensus on how to make that effing \& effable? I'm still for "non-printing, zero-width character." -- Pe

Re: warning on mid-input line sentence endings (was: Warn on semantic newlines)

2022-07-17 Thread G. Branden Robinson
At 2022-07-17T09:18:28-0500, Dave Kemper wrote: > On 7/16/22, G. Branden Robinson wrote: > > I think a new, writable troff register would be a better way to > > manipulate this feature--which is basically a style diagnostic--than > > a warning category. > > This suggests that one day there might

Re: warning on mid-input line sentence endings

2022-07-17 Thread Dave Kemper
On 7/17/22, Douglas McIlroy wrote: > In regard to turning the warning on or off, the warning should not be > given when sentence spacing is set to 0 (or below some small > threshold). Since the proposal (now filed as http://savannah.gnu.org/bugs/?62776) gives the user the power to turn the warnin

Re: warning on mid-input line sentence endings

2022-07-17 Thread G. Branden Robinson
Hi Doug! At 2022-07-17T09:06:53-0400, Douglas McIlroy wrote: > In regard to turning the warning on or off, the warning should not be > given when sentence spacing is set to 0 (or below some small > threshold). In that case the opposite warning would be appropriate--a > double space between sentenc

Re: warning on mid-input line sentence endings (was: Warn on semantic newlines)

2022-07-17 Thread Dave Kemper
On 7/16/22, G. Branden Robinson wrote: > I think a new, writable troff register would > be a better way to manipulate this feature--which is basically a style > diagnostic--than a warning category. This suggests that one day there might be other warnings that fall into the style-diagnostic catego

Re: warning on mid-input line sentence endings

2022-07-17 Thread Douglas McIlroy
In regard to turning the warning on or off, the warning should not be given when sentence spacing is set to 0 (or below some small threshold). In that case the opposite warning would be appropriate--a double space between sentences is questionable when sentence spacing is 0. Doug

warning on mid-input line sentence endings (was: Warn on semantic newlines)

2022-07-16 Thread G. Branden Robinson
[I've retitled the subject line to avoid misleading terminology.] At 2022-06-10T07:16:54-0500, G. Branden Robinson wrote: > At 2022-06-10T11:52:30+0200, Alejandro Colomar wrote: > > As far as I know, there's currently no tool that warns on "foo. bar" > > in filled test. Not `mandoc -Tlint`, and n