From: Paul Pogonyshev <pogonyshev@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Gregory Heytings <gregory@heytings.org>,
57804@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#57804: An infinite loop in a `fontify-region' function causes Emacs to hang indefinitely
Date: Fri, 16 Sep 2022 12:08:49 +0200 [thread overview]
Message-ID: <CAG7Bpap4=M_dbJj-bxvSmwtxb2T8a+yOvW+nZUHB5ZGP7p2FRw@mail.gmail.com> (raw)
In-Reply-To: <83mtaz4ya5.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1926 bytes --]
I give up. Do as you like.
Paul
On Fri, 16 Sept 2022 at 08:40, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Paul Pogonyshev <pogonyshev@gmail.com>
> > Date: Fri, 16 Sep 2022 00:53:37 +0200
> > Cc: Eli Zaretskii <eliz@gnu.org>, 57804@debbugs.gnu.org, Lars
> Ingebrigtsen <larsi@gnus.org>
> >
> > > It is for example possible to parse the buffer outside of
> > > fontification-functions
> >
> > You are ignoring that this is not only about fontification. It can
> > happen anywhere, because I may need full access to the buffer at any
> > time.
>
> Your mode is requested to be able to run in some kind of "simplified
> mode" when long-line-threshold is exceeded, in a way that doesn't
> require such full access.
>
> > > Yet another method would be to use a simpler fontification method in
> > > buffers with too long lines. Yet another method would be to turn
> > > font locking off in buffers with too long lines.
> >
> > I don't want to lose fontification in a 10 MB buffer because one line
> > somewhere there is over 10000 characters.
>
> The locked restriction leaves accessible a region of the buffer that
> is quite large. So if you are fontifying a line that is not very long
> in such a buffer, you should still be able to access enough text
> before and after the window to be able to fontify. It is expected
> that modes which need to access more than that will be amended to
> perform, perhaps sub-optimally, in such cases. In extreme cases, you
> can simply not fontify if there's no reasonable way of fontifying even
> approximately. (I don't believe such extreme measures should be
> necessary, but they are a possibility.)
>
> IOW, we fully expect that in some cases and with some features, there
> will be partial loss of functionality in these cases. We consider
> that still much better than a locked-up Emacs that can only be killed.
>
> > Security against what, for fuck's sake?
>
> Language!
>
[-- Attachment #2: Type: text/html, Size: 2683 bytes --]
next prev parent reply other threads:[~2022-09-16 10:08 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 15:05 bug#57804: An infinite loop in a `fontify-region' function causes Emacs to hang indefinitely Paul Pogonyshev
2022-09-14 16:00 ` dick
2022-09-14 16:06 ` Paul Pogonyshev
2022-09-14 16:14 ` dick
2022-09-14 17:52 ` Lars Ingebrigtsen
2022-09-14 18:18 ` Eli Zaretskii
2022-09-14 16:41 ` Lars Ingebrigtsen
2022-09-14 16:57 ` Paul Pogonyshev
2022-09-14 17:25 ` Lars Ingebrigtsen
2022-09-14 17:30 ` Paul Pogonyshev
2022-09-14 17:43 ` Eli Zaretskii
2022-09-14 17:45 ` Lars Ingebrigtsen
2022-09-14 17:49 ` Eli Zaretskii
2022-09-15 2:17 ` Ihor Radchenko
2022-09-14 17:34 ` Gregory Heytings
2022-09-15 14:47 ` Paul Pogonyshev
2022-09-15 15:10 ` Gregory Heytings
2022-09-15 15:37 ` Paul Pogonyshev
2022-09-15 16:08 ` Gregory Heytings
2022-09-15 16:19 ` Paul Pogonyshev
2022-09-15 16:44 ` Gregory Heytings
2022-09-15 18:49 ` Paul Pogonyshev
2022-09-15 19:16 ` Eli Zaretskii
2022-09-15 19:36 ` Paul Pogonyshev
2022-09-15 19:45 ` Eli Zaretskii
2022-09-15 20:18 ` Gregory Heytings
2022-09-15 20:22 ` Lars Ingebrigtsen
2022-09-15 20:40 ` Paul Pogonyshev
2022-09-15 20:44 ` Gregory Heytings
2022-09-15 21:17 ` Paul Pogonyshev
2022-09-15 21:32 ` Gregory Heytings
2022-09-15 21:49 ` Paul Pogonyshev
2022-09-15 22:16 ` Gregory Heytings
2022-09-15 22:53 ` Paul Pogonyshev
2022-09-15 23:13 ` Gregory Heytings
2022-09-16 6:40 ` Eli Zaretskii
2022-09-16 10:08 ` Paul Pogonyshev [this message]
2022-09-16 10:44 ` Eli Zaretskii
2022-09-16 6:31 ` Eli Zaretskii
[not found] ` <1260fd38-d4b3-5ca1-5b15-78f59c0255b6@yandex.ru>
[not found] ` <83o7t9k8fr.fsf@gnu.org>
[not found] ` <CAG7Bpaow570a8Qrq6VxU+=MNF55UmnCMFFXT2Eg=vQUTgrxeoQ@mail.gmail.com>
[not found] ` <34e17bf2a6bdd269fba7@heytings.org>
[not found] ` <CAG7BpapFE0HEwi8iUoStz9EyAwH-QdZ_CxOUNtdUeKDmzCrZaQ@mail.gmail.com>
[not found] ` <338f50d421074805735f@heytings.org>
[not found] ` <831qpnngeg.fsf@gnu.org>
[not found] ` <338f50d421b672315145@heytings.org>
2022-11-28 18:32 ` Eli Zaretskii
2022-09-16 1:17 ` Ihor Radchenko
2022-09-16 5:35 ` Eli Zaretskii
2022-09-15 19:44 ` Gregory Heytings
2022-09-15 20:07 ` Paul Pogonyshev
2022-09-15 20:26 ` Gregory Heytings
2022-09-16 5:37 ` Eli Zaretskii
2022-09-15 22:20 ` dick
2022-09-15 22:38 ` Gregory Heytings
2022-09-16 6:19 ` Eli Zaretskii
2022-09-16 7:44 ` Gerd Möllmann
2022-09-14 17:02 ` Eli Zaretskii
2022-09-14 17:25 ` Paul Pogonyshev
2022-09-14 17:32 ` Eli Zaretskii
2022-09-14 17:38 ` Lars Ingebrigtsen
2022-09-14 17:44 ` Eli Zaretskii
2022-09-14 17:46 ` Lars Ingebrigtsen
2022-09-14 17:51 ` Eli Zaretskii
2022-09-15 5:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-15 6:27 ` Eli Zaretskii
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='CAG7Bpap4=M_dbJj-bxvSmwtxb2T8a+yOvW+nZUHB5ZGP7p2FRw@mail.gmail.com' \
--to=pogonyshev@gmail.com \
--cc=57804@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gregory@heytings.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 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).