unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel@gnu.org
Subject: tree-sitter branch broken
Date: Sat, 29 Oct 2022 11:09:08 +0300	[thread overview]
Message-ID: <83bkpvhx0b.fsf@gnu.org> (raw)

The current branch seems to be broken by the penultimate commit:

    ELC      treesit.elc

  In end of data:
  treesit.el: Warning: the function `,' is not known to be defined.
  make[3]: Leaving directory `/d/gnu/git/emacs/feature/lisp'
  make[3]: Entering directory `/d/gnu/git/emacs/feature/lisp'
  make[3]: Nothing to be done for `compile-targets'.
  make[3]: Leaving directory `/d/gnu/git/emacs/feature/lisp'
  make[3]: Entering directory `/d/gnu/git/emacs/feature/lisp'
    ELC      progmodes/js.elc
    ELC      progmodes/python.elc
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled
  Function provided is already compiled

It compiles cleanly if I revert the last two commits.



             reply	other threads:[~2022-10-29  8:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-29  8:09 Eli Zaretskii [this message]
2022-10-29  8:26 ` tree-sitter branch broken Theodor Thornhill via Emacs development discussions.
2022-10-29 16:12   ` Yuan Fu

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=83bkpvhx0b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@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.
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).