unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Where to get language definition for bash tree-sitter?
Date: Fri, 30 Dec 2022 08:23:20 +0300	[thread overview]
Message-ID: <Y651yOuPhV98ui7g@protected.localdomain> (raw)
In-Reply-To: <83wn6b8ndn.fsf@gnu.org>

* Eli Zaretskii <eliz@gnu.org> [2022-12-28 20:12]:
> > Date: Wed, 28 Dec 2022 12:05:11 +0300
> > From: Jean Louis <bugs@gnu.support>
> > Cc: help-gnu-emacs@gnu.org
> > 
> > I got these after compiling:
> > 
> >   -rw-r--r-- 1 476K Dec 28 11:32 parser.o
> >   -rw-r--r-- 1 6.7K Dec 28 11:32 scanner.o
> > 
> > How do I link them?
> > 
> > gcc -shared maybe, but I know gcc just like you know Org.
> 
> I don't know exactly how to do that on your system, and don't want to
> get you in trouble with stuff you aren't familiar with.  Sorry.
> Perhaps someone else will be able to help.
> 
> (In general, if you don't know how to build a shared library on your
> system, my recommendation would be to wait for your distro to offer
> these grammar libraries ready to install.  No disaster will happen if
> you delay experiencing tree-sitter and the features it supports until
> your distro provides that.)

Of course I will not wait, it would defeat purpose of the question.

I will find way.

--
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/




      reply	other threads:[~2022-12-30  5:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27 10:21 Where to get language definition for bash tree-sitter? Jean Louis
2022-12-27 11:43 ` Emanuel Berg
2022-12-27 12:43 ` Eli Zaretskii
2022-12-27 13:35   ` Jean Louis
2022-12-27 14:02     ` Emanuel Berg
2022-12-27 14:14     ` Eli Zaretskii
2022-12-27 17:08       ` Jean Louis
2022-12-27 18:10         ` Eli Zaretskii
2022-12-28  9:05           ` Jean Louis
2022-12-28 17:11             ` Eli Zaretskii
2022-12-30  5:23               ` Jean Louis [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

  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=Y651yOuPhV98ui7g@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).