bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#17321: 24.3.50; Fill paragraph fails with period in fill-column


From: Stefan Kangas
Subject: bug#17321: 24.3.50; Fill paragraph fails with period in fill-column
Date: Sun, 10 Oct 2021 16:01:31 -0700
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.60 (gnu/linux)

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>>      ;; Don't break after a period followed by just one space.
>>>      ;; Move back to the previous place to break.
>>>      ;; The reason is that if a period ends up at the end of a
>>>      ;; line, further fills will assume it ends a sentence.
>>>      ;; If we now know it does not end a sentence, avoid putting
>>>      ;; it at the end of the line.
>>
>> It's likely that this is causing the problem, but I'm not convinced that
>> it justifies the current behavior.  IOW, I think it's just a bug.
>
> Ah, this explains the weird behaviour I see from time to time.
>
> If I have
>
> Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eius.|
>
> then his a space, I get
>
> Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do
> eius. |
>
> Then I type on
>
> Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do
> eius.  Ut enim ad|
>
> And then hitting `M-q' gives me
>
> Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eius.
> Ut enim ad|
>
> Anybody against changing this odd behaviour in `fill-nobreak-p'?  It's
> not quite clear what the overall repercussions would be, though.

No complaints here.  :-)

The most annoying thing is that it does this:

    Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do
    eius.  Ut enim ad|

Pressing M-q leads to:

    Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eius.
    Ut enim ad|

Pressing M-q again leads to:

    Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do
    eius. Ut enim ad|

It would IMO be really good if we could avoid this.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]