unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63762@debbugs.gnu.org
Subject: bug#63762: 29.0.91; tty emacs on macOS fail to load tree-sitter
Date: Sun, 28 May 2023 10:47:41 +0100	[thread overview]
Message-ID: <CAKDRQS4TftkF1iEQ9vXm8MrBQorDCOBptO++0=VL0BG5ZrswEQ@mail.gmail.com> (raw)
In-Reply-To: <83bki4iyf7.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 863 bytes --]

Nope, it's all automatic. Something somewhere in the NS port is setting
`treesit-extra-load-path' correctly, despite both ports were compiled with
LDFLAGS='-L/opt/local/lib'

Jimmy


On Sun, May 28, 2023 at 10:42 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
> > Date: Sun, 28 May 2023 10:27:16 +0100
> > Cc: 63762@debbugs.gnu.org
> >
> > gdb doesn't work with clang and I have a hard time using lldb, all I can
> say for sure is, for some
> > reason, `treesit-extra-load-path' is nil when running TTY emacs on
> macOS, whereas it is set to '
> > ("/opt/local/lib") on the NS port.
>
> treesit-extra-load-path is nil in my session, and that is its normal
> value.  How did you get it set to something non-nil in the NS build?
> I see nothing in the sources, so maybe it's your customizations?
>

[-- Attachment #2: Type: text/html, Size: 1463 bytes --]

  reply	other threads:[~2023-05-28  9:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27 23:46 bug#63762: 29.0.91; tty emacs on macOS fail to load tree-sitter Jimmy Yuen Ho Wong
2023-05-28  5:36 ` Eli Zaretskii
2023-05-28  8:15   ` Jimmy Yuen Ho Wong
2023-05-28  8:31     ` Eli Zaretskii
2023-05-28  9:27       ` Jimmy Yuen Ho Wong
2023-05-28  9:43         ` Eli Zaretskii
2023-05-28  9:47           ` Jimmy Yuen Ho Wong [this message]
2023-05-28  9:50             ` Jimmy Yuen Ho Wong
2023-05-28 10:18               ` 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='CAKDRQS4TftkF1iEQ9vXm8MrBQorDCOBptO++0=VL0BG5ZrswEQ@mail.gmail.com' \
    --to=wyuenho@gmail.com \
    --cc=63762@debbugs.gnu.org \
    --cc=eliz@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).