bug#11322: closed (24.0.95; hs-find-block-beginning failure)

[GNU bug Tracking System]

Your message dated Wed, 25 Nov 2020 02:35:17 -0800
with message-id 
<CADwFkmkUAe=tecjoasWmDwyQRx-GHdmqnnY2RszSr1iPmXpqfA@mail.gmail.com>
and subject line Re: bug#11322: 24.0.95; hs-find-block-beginning failure
has caused the debbugs.gnu.org bug report #11322,
regarding 24.0.95; hs-find-block-beginning failure
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
11322: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11322
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 24.0.95; hs-find-block-beginning failure
>
>
>
>
> Date: 
>
> Tue, 24 Apr 2012 13:10:53 +0800
>
>
>
>
> hs-find-block-beginning finds the wrong beginning when point is inside
> hs-block-start-regexp.
>
> Leo
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#11322: 24.0.95; hs-find-block-beginning failure
>
>
>
>
> Date: 
>
> Wed, 25 Nov 2020 02:35:17 -0800
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
>
>
>
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > Leo Liu <sdl.web@gmail.com> writes:
> >
> >> On 2019-11-01 20:55 +0100, Stefan Kangas wrote:
> >>> I was unable to reproduce this on current master, but perhaps I'm
> >>> failing to understand what I'm supposed to do.
> >>
> >> What did you try?
> >>
> >> To reproduce the bug you need a hs regexp that matches more than chars
> >> and have the point in it. But I don't have a step-by-step recipe to
> >> reproduce it though the description seems to give enough info.
> >
> > The description doesn't seem to give enough info?  Could you please try
> > to give step by step instructions on how to reproduce the bug, starting
> > from "emacs -Q"?
>
> More information was requested, but none was given within 9 weeks, so
> I'm closing this bug.  If this is still an issue, please reply to this
> email (use "Reply to all" in your email client) and we can reopen the
> bug report.
>
>
> --- End Message ---