From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs freezes again when I try to open a file including only one very long line.
Date: Wed, 29 Jun 2022 19:03:53 +0300 [thread overview]
Message-ID: <831qv778ye.fsf@gnu.org> (raw)
In-Reply-To: <CAGP6POLV5EFFYPjaK-s_7VOOr+mO3ewxunFrGu2ExbMH9Hi1SA@mail.gmail.com> (message from Hongyi Zhao on Wed, 29 Jun 2022 22:30:47 +0800)
> From: Hongyi Zhao <hongyi.zhao@gmail.com>
> Date: Wed, 29 Jun 2022 22:30:47 +0800
> Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
>
> OK. Let me take a concrete result as an example. If I search
> `|isgroup|', then VSCode will give the only result immediately as
> shown in the attached file. Now, how can I achieve this in Emacs?
Maybe you can't, it depends on how deep into the file that match is
and how fast is your system (if it's very fast, try enlarging the
value of max-redisplay-ticks).
But you are asking questions that are not relevant to what this
feature does. This feature prevents Emacs from freezing when you
visit such files. That is all it does. As I tried explaining several
times already.
next prev parent reply other threads:[~2022-06-29 16:03 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 0:51 Emacs freezes again when I try to open a file including only one very long line Hongyi Zhao
2022-06-27 1:58 ` Emanuel Berg
2022-06-27 2:29 ` Eli Zaretskii
2022-06-27 2:36 ` Hongyi Zhao
2022-06-27 11:02 ` Eli Zaretskii
2022-06-27 11:22 ` Hongyi Zhao
[not found] ` <CAGP6POKVBGL+gKOLAcqPxgFKzAC9bObW-Hzz-pWCj6mpxtCnAg@mail.gmail.com>
[not found] ` <83tu856ny2.fsf@gnu.org>
2022-06-28 12:56 ` Hongyi Zhao
2022-06-28 13:11 ` Eli Zaretskii
2022-06-28 13:56 ` Hongyi Zhao
2022-06-28 14:18 ` Eli Zaretskii
2022-06-28 14:38 ` Hongyi Zhao
2022-06-28 15:53 ` Eli Zaretskii
2022-06-29 1:05 ` Hongyi Zhao
2022-06-29 1:35 ` Emanuel Berg
2022-06-29 2:36 ` Eli Zaretskii
2022-06-29 2:48 ` Hongyi Zhao
2022-06-29 11:16 ` Eli Zaretskii
2022-06-29 11:25 ` Hongyi Zhao
2022-06-29 11:37 ` Eli Zaretskii
2022-06-29 12:22 ` Hongyi Zhao
2022-06-29 14:11 ` Eli Zaretskii
2022-06-29 14:30 ` Hongyi Zhao
2022-06-29 16:03 ` Eli Zaretskii [this message]
2022-06-30 0:38 ` Hongyi Zhao
2022-06-30 5:41 ` Hongyi Zhao
2022-06-30 12:09 ` Michael Heerdegen
2022-06-30 12:52 ` Michael Heerdegen
2022-06-30 13:56 ` Eli Zaretskii
2022-06-30 14:16 ` Michael Heerdegen
2022-06-30 14:22 ` Eli Zaretskii
2022-06-30 14:32 ` Michael Heerdegen
2022-06-30 15:54 ` Eli Zaretskii
2022-06-30 14:36 ` Michael Heerdegen
2022-06-30 16:04 ` Eli Zaretskii
2022-07-01 11:17 ` Michael Heerdegen
2022-06-29 6:44 ` Manuel Giraud
2022-06-29 11:20 ` Eli Zaretskii
2022-06-30 8:29 ` Manuel Giraud
2022-06-30 12:02 ` Manuel Giraud
2022-06-30 12:43 ` Emanuel Berg
2022-06-30 12:53 ` Emanuel Berg
2022-06-30 13:35 ` Manuel Giraud
2022-06-30 13:36 ` Hongyi Zhao
2022-06-30 13:40 ` Eli Zaretskii
2022-06-28 15:06 ` Emanuel Berg
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831qv778ye.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.
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).