unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Tassilo Horn" <tsdh@gnu.org>
To: "Eli Zaretskii" <eliz@gnu.org>,
	"Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: yantar92@posteo.net, 70796@debbugs.gnu.org
Subject: bug#70796: 30.0.50; bug-reference-mode leading to constant GCing
Date: Sat, 18 May 2024 17:49:15 +0200	[thread overview]
Message-ID: <e1eed280-386c-4ea6-913b-ed0c4cd2e873@betaapp.fastmail.com> (raw)
In-Reply-To: <86bk53fsq1.fsf@gnu.org>

Hi all,

it's the first day of my vacation so I'm away from the computer until next Saturday evening at best. But then I'll have a look. 

Bye, 
Tassilo 

Am Sa, 18. Mai 2024, um 10:07, schrieb Eli Zaretskii:
>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: Ihor Radchenko <yantar92@posteo.net>,  70796@debbugs.gnu.org
>> Date: Sat, 18 May 2024 08:27:15 +0200
>> 
>> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>> 
>> > Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>> >
>> >> Eli Zaretskii <eliz@gnu.org> writes:
>> >>
>> >>> So I'm not sure which part(s) of bug-reference.el make a lot of
>> >>> garbage, or why.
>> >>
>> >> This maybe completely wrong, but my suspicion was that bug-reference
>> >> somehow triggers Org fontification, which creates more garbage. If
>> >> that's possible...
>> >
>> > Maybe bug-reference-fontify should return a list (jit-lock-bounds beg
>> > end)? Looks to me like if it doesn't we could end up fontifying the
>> > whole buffer for Org. See jit-lock--run-functions.
>> >
>> > Not sure but the behaviour looks like somethign like that could be
>> > happening.
>> 
>> Ping
>
> Tassilo, could you please take a look at this?





  reply	other threads:[~2024-05-18 15:49 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  6:53 bug#70796: 30.0.50; bug-reference-mode leading to constant GCing Gerd Möllmann
2024-05-06 11:48 ` Eli Zaretskii
2024-05-06 12:35   ` Gerd Möllmann
2024-05-06 14:03     ` Eli Zaretskii
2024-05-06 14:09       ` Gerd Möllmann
2024-05-07  6:58         ` Gerd Möllmann
2024-05-18  6:27           ` Gerd Möllmann
2024-05-18  8:07             ` Eli Zaretskii
2024-05-18 15:49               ` Tassilo Horn [this message]
2024-05-24 20:00               ` Tassilo Horn
2024-05-24 20:19                 ` Gerd Möllmann
2024-05-24 20:28                   ` Ihor Radchenko
2024-05-25  4:08                     ` Gerd Möllmann
2024-05-24 21:34                   ` Tassilo Horn
2024-05-25  4:34                     ` Gerd Möllmann
2024-05-25  7:37                       ` Tassilo Horn
2024-05-25  7:58                         ` Gerd Möllmann
2024-05-25  8:17                           ` Tassilo Horn
2024-06-01  9:05                             ` Gerd Möllmann
2024-06-15  7:54                               ` Eli Zaretskii
2024-06-15  8:07                                 ` Gerd Möllmann
2024-06-16  9:45                                   ` Tassilo Horn
2024-06-16 10:44                                     ` Eli Zaretskii
2024-06-17  7:34                                       ` Andrea Corallo
2024-06-17  8:07                                         ` Andrea Corallo
2024-06-17  8:19                                           ` Tassilo Horn
2024-06-17  8:30                                             ` Andrea Corallo
2024-06-17  9:02                                               ` Gerd Möllmann
2024-06-17  9:30                                                 ` Andrea Corallo
2024-06-17  9:53                                                   ` Gerd Möllmann
2024-06-17 10:10                                                     ` Andrea Corallo
2024-06-17 10:33                                                       ` Gerd Möllmann
2024-06-17 14:13                                                         ` Andrea Corallo
2024-06-17  8:21                                           ` Gerd Möllmann

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=e1eed280-386c-4ea6-913b-ed0c4cd2e873@betaapp.fastmail.com \
    --to=tsdh@gnu.org \
    --cc=70796@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=yantar92@posteo.net \
    /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).