unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#50406: fill-paragraph error
@ 2021-09-05 16:10 Juri Linkov
  2021-09-06  9:18 ` Lars Ingebrigtsen
  2022-08-22 20:46 ` Lars Ingebrigtsen
  0 siblings, 2 replies; 6+ messages in thread
From: Juri Linkov @ 2021-09-05 16:10 UTC (permalink / raw)
  To: 50406

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

Please try to open the attached file in emacs -Q, and after moving point
to the beginning of the 3rd line, type 'M-q'.  When debug-on-error is t,
it fails with such backtrace:

Debugger entered--Lisp error: (error "Invalid search bound (wrong side of point)")
  re-search-backward("[ \11]\\|\\c|.\\|.\\c|" 280 0)
  fill-move-to-break-point(280)
  fill-region-as-paragraph(184 210 nil nil 186)
  fill-comment-paragraph(nil)
  fill-paragraph(nil t)
  funcall-interactively(fill-paragraph nil t)
  command-execute(fill-paragraph)

BTW, evaluating debug-on-error in *scratch* shows t by default,
but 'C-h v debug-on-error' shows it's nil actually, strange.


[-- Attachment #2: fill-paragraph --]
[-- Type: application/octet-stream, Size: 209 bytes --]

; -*- comment-start: "; "; fill-column: 75; indent-tabs-mode: nil; truncate-lines: t; -*-

abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc ; def def def def def ghi

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#50406: fill-paragraph error
  2021-09-05 16:10 bug#50406: fill-paragraph error Juri Linkov
@ 2021-09-06  9:18 ` Lars Ingebrigtsen
  2021-09-06 15:14   ` Juri Linkov
  2022-08-22 20:46 ` Lars Ingebrigtsen
  1 sibling, 1 reply; 6+ messages in thread
From: Lars Ingebrigtsen @ 2021-09-06  9:18 UTC (permalink / raw)
  To: Juri Linkov; +Cc: 50406

Juri Linkov <juri@linkov.net> writes:

> Please try to open the attached file in emacs -Q, and after moving point
> to the beginning of the 3rd line, type 'M-q'.  When debug-on-error is t,
> it fails with such backtrace:
>
> Debugger entered--Lisp error: (error "Invalid search bound (wrong side
> of point)")
>   re-search-backward("[ \11]\\|\\c|.\\|.\\c|" 280 0)
>   fill-move-to-break-point(280)

I can reproduce this bug, too.

> BTW, evaluating debug-on-error in *scratch* shows t by default,
> but 'C-h v debug-on-error' shows it's nil actually, strange.

With `C-x C-e'?  Then this happens:

---
If ‘eval-expression-debug-on-error’ is non-nil, which is the default,
this command arranges for all errors to enter the debugger.
---


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#50406: fill-paragraph error
  2021-09-06  9:18 ` Lars Ingebrigtsen
@ 2021-09-06 15:14   ` Juri Linkov
  0 siblings, 0 replies; 6+ messages in thread
From: Juri Linkov @ 2021-09-06 15:14 UTC (permalink / raw)
  To: Lars Ingebrigtsen; +Cc: 50406

>> Debugger entered--Lisp error: (error "Invalid search bound (wrong side
>> of point)")
>>   re-search-backward("[ \11]\\|\\c|.\\|.\\c|" 280 0)
>>   fill-move-to-break-point(280)
>
> I can reproduce this bug, too.
>
>> BTW, evaluating debug-on-error in *scratch* shows t by default,
>> but 'C-h v debug-on-error' shows it's nil actually, strange.
>
> With `C-x C-e'?

Yep.

> Then this happens:
>
> ---
> If ‘eval-expression-debug-on-error’ is non-nil, which is the default,
> this command arranges for all errors to enter the debugger.
> ---

This is fine, just a little strange.





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#50406: fill-paragraph error
  2021-09-05 16:10 bug#50406: fill-paragraph error Juri Linkov
  2021-09-06  9:18 ` Lars Ingebrigtsen
@ 2022-08-22 20:46 ` Lars Ingebrigtsen
  2022-08-23  7:35   ` Juri Linkov
  1 sibling, 1 reply; 6+ messages in thread
From: Lars Ingebrigtsen @ 2022-08-22 20:46 UTC (permalink / raw)
  To: Juri Linkov; +Cc: 50406

Juri Linkov <juri@linkov.net> writes:

> Please try to open the attached file in emacs -Q, and after moving point
> to the beginning of the 3rd line, type 'M-q'.  When debug-on-error is t,
> it fails with such backtrace:
>
> Debugger entered--Lisp error: (error "Invalid search bound (wrong side
> of point)")
>   re-search-backward("[ \11]\\|\\c|.\\|.\\c|" 280 0)
>   fill-move-to-break-point(280)
>   fill-region-as-paragraph(184 210 nil nil 186)
>   fill-comment-paragraph(nil)
>   fill-paragraph(nil t)
>   funcall-interactively(fill-paragraph nil t)
>   command-execute(fill-paragraph)

This doesn't happen now in Emacs 29.  Instead I get:

abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc ; def
											    ; def
											    ; def
											    ; def
											    ; def
											    ; ghi

Is that the result we're supposed to get, though?  I'm not at all sure
how fill-paragraph/comment-start are supposed to interact here.






^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#50406: fill-paragraph error
  2022-08-22 20:46 ` Lars Ingebrigtsen
@ 2022-08-23  7:35   ` Juri Linkov
  2022-08-23 10:46     ` Lars Ingebrigtsen
  0 siblings, 1 reply; 6+ messages in thread
From: Juri Linkov @ 2022-08-23  7:35 UTC (permalink / raw)
  To: Lars Ingebrigtsen; +Cc: 50406

>> Please try to open the attached file in emacs -Q, and after moving point
>> to the beginning of the 3rd line, type 'M-q'.  When debug-on-error is t,
>> it fails with such backtrace:
>>
>> Debugger entered--Lisp error: (error "Invalid search bound (wrong side
>> of point)")
>>   re-search-backward("[ \11]\\|\\c|.\\|.\\c|" 280 0)
>>   fill-move-to-break-point(280)
>>   fill-region-as-paragraph(184 210 nil nil 186)
>>   fill-comment-paragraph(nil)
>>   fill-paragraph(nil t)
>>   funcall-interactively(fill-paragraph nil t)
>>   command-execute(fill-paragraph)
>
> This doesn't happen now in Emacs 29.  Instead I get:
>
> abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc abc ; def
> 											    ; def
> 											    ; def
> 											    ; def
> 											    ; def
> 											    ; ghi
>
> Is that the result we're supposed to get, though?  I'm not at all sure
> how fill-paragraph/comment-start are supposed to interact here.

This is what it always did in all earlier versions until the recent
breakage that is fixed now.





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#50406: fill-paragraph error
  2022-08-23  7:35   ` Juri Linkov
@ 2022-08-23 10:46     ` Lars Ingebrigtsen
  0 siblings, 0 replies; 6+ messages in thread
From: Lars Ingebrigtsen @ 2022-08-23 10:46 UTC (permalink / raw)
  To: Juri Linkov; +Cc: 50406

Juri Linkov <juri@linkov.net> writes:

> This is what it always did in all earlier versions until the recent
> breakage that is fixed now.

OK, then I guess everything works here, and I'm closing this bug report.





^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2022-08-23 10:46 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-09-05 16:10 bug#50406: fill-paragraph error Juri Linkov
2021-09-06  9:18 ` Lars Ingebrigtsen
2021-09-06 15:14   ` Juri Linkov
2022-08-22 20:46 ` Lars Ingebrigtsen
2022-08-23  7:35   ` Juri Linkov
2022-08-23 10:46     ` Lars Ingebrigtsen

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).