From: Evgeny Zajcev <lg.zevlg@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 47338@debbugs.gnu.org
Subject: bug#47338: 28.0.50; Unexpected error in fill-region
Date: Thu, 25 Mar 2021 21:27:43 +0300 [thread overview]
Message-ID: <CAO=W_Zp82HgchtOsNoh7qJV=TaWTcwLz8sFpu2T=ao6ua5Nc4g@mail.gmail.com> (raw)
In-Reply-To: <87o8f8ewf3.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
ср, 24 мар. 2021 г. в 12:24, Lars Ingebrigtsen <larsi@gnus.org>:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > This is the result of fixing bug#45720. In the above scenario, the
> > first time through the loop LINEBEG in the fragment below is set to
> > EOB+1 instead of the point where the fill-prefix ends:
> >
> > (let ((first t)
> > linebeg)
> > (while (< (point) to)
> > ;; On the first line, there may be text in the fill prefix
> > ;; zone. In that case, don't consider that area when
> > ;; trying to find a place to put a line break (bug#45720).
> > (if (not first)
> > (setq linebeg (point))
> > (setq first nil
> > linebeg (+ (point) (length fill-prefix)))) <<<<<<<<<<
> >
> > CC'ing Lars who made that change.
>
> Right... the change tried to fix the case where there's a pre-computed
> fill prefix being passed in. In this bug, however, the prefix is
> computed, and this logic shouldn't be done here. I've now fixed this in
> Emacs 28, but I'm still not quite sure about the original fix...
>
>
Thanks! this works perfectly for me
--
lg
[-- Attachment #2: Type: text/html, Size: 1874 bytes --]
prev parent reply other threads:[~2021-03-25 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 9:43 bug#47338: 28.0.50; Unexpected error in fill-region Evgeny Zajcev
2021-03-23 15:31 ` bug#47338: [External] : " Drew Adams
2021-03-23 16:44 ` Eli Zaretskii
2021-03-23 17:19 ` Drew Adams
2021-03-23 17:55 ` Gregory Heytings
2021-03-23 19:24 ` Eli Zaretskii
2021-03-23 19:42 ` Gregory Heytings
2021-03-23 18:05 ` Eli Zaretskii
2021-03-24 9:24 ` Lars Ingebrigtsen
2021-03-25 18:27 ` Evgeny Zajcev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO=W_Zp82HgchtOsNoh7qJV=TaWTcwLz8sFpu2T=ao6ua5Nc4g@mail.gmail.com' \
--to=lg.zevlg@gmail.com \
--cc=47338@debbugs.gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.