On Wed, Jun 29, 2022 at 7:17 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Hongyi Zhao <hongyi.zhao@gmail.com>
> > Date: Wed, 29 Jun 2022 10:48:16 +0800
> > Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
> >
> > On Wed, Jun 29, 2022 at 10:36 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > > > Therefore, Emacs still cannot properly handle this situation
> > > > practically, at least for the user's point of view.
> > >
> > > Actually, it _can_ handle this situation "practically", in that now it
> > > doesn't freeze the entire session, thus allowing the user to do
> > > something about the issue without losing any edits.
> >
> > I still don't understand what you mean.
>
> I mean Emacs is no longer frozen.  This is the only practical handling
> of this situation that we could provide for such files.
>
> > For example, how to get the same incremental search results
> > displayed in real time as what in the vscode I showed.
>
> The results of incremental search are shown as long as displaying them
> takes a reasonable amount of time.  When Emacs is no longer capable of
> displaying the results in reasonable time (a.k.a. "freezes"), the
> results are no longer displayed, to give you a responsive Emacs
> session.

But I waited a minute and didn't see any matching results highlighted
on the screen, as shown in the attached file.
BTW, all the matched results will be displayed in vscode almost at the
same time as the input.

Yours,
Hongsheng