all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jacob Faibussowitsch <jacob.fai@gmail.com>
Cc: 50338@debbugs.gnu.org
Subject: bug#50338: [Emacs 28.0.50 Trunk] Error running timer ‘jit-lock-stealth-fontify’: wrong-type-argument timerp
Date: Thu, 02 Sep 2021 18:26:39 +0200	[thread overview]
Message-ID: <87tuj354g0.fsf@gnus.org> (raw)
In-Reply-To: <06EB8D55-C9F4-425B-BF2D-20A8998F6165@gmail.com> (Jacob Faibussowitsch's message of "Thu, 2 Sep 2021 11:17:41 -0500")

Jacob Faibussowitsch <jacob.fai@gmail.com> writes:

> On a related note: I pull emacs trunk regularly but rebuild and reinstall
> maybe weekly so should I always be doing make bootstrap?

No, a bootstrap is normally not necessary, but the Emacs build system is
far from perfect.  The problem is that if we alter a macro in foo.el,
and bar.el requires foo, then foo.elc will be rebuilt, but bar.elc won't
be.  And this can lead to breakages (as it did in this instance).

But we don't change macros that much, so a bootstrap is seldom necessary.

I think there's an open bug report somewhere about fixing this, but I
don't think anybody has come up with a practical idea here (i.e.,
building a dependency graph in an efficient way).

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-09-02 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 15:00 bug#50338: [Emacs 28.0.50 Trunk] Error running timer ‘jit-lock-stealth-fontify’: wrong-type-argument timerp Jacob Faibussowitsch
2021-09-02 16:01 ` Lars Ingebrigtsen
2021-09-02 16:17   ` Jacob Faibussowitsch
2021-09-02 16:26     ` Lars Ingebrigtsen [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tuj354g0.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=50338@debbugs.gnu.org \
    --cc=jacob.fai@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.