[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Tree-sitter api
From: |
Yuan Fu |
Subject: |
Re: Tree-sitter api |
Date: |
Thu, 31 Mar 2022 09:35:32 -0700 |
>
> If so, I think we should have our own load-path for these
> libraries; relying on the standard LD_LIBRARY_PATH etc. is not good
> enough (although we should support that as well). I envision that at
> least in some cases users will not want to have these libraries in the
> public places, or maybe even won't have the requisite access rights to
> do so. We should provide Emacs-style alternatives, like some
> subdirectory of ~/.emacs.d/ and/or under ${prefix}/lib/ (similar to
> *.eln files).
Anyone has thoughts on this?
Yuan
- Re: Tree-sitter api, (continued)
- Re: Tree-sitter api, Richard Stallman, 2022/03/31
- Re: Tree-sitter api, Eli Zaretskii, 2022/03/31
- Re: Tree-sitter api, Lars Ingebrigtsen, 2022/03/31
- Re: Tree-sitter api, John Yates, 2022/03/31
- Re: Tree-sitter api, Phil Sainty, 2022/03/31
- Re: Tree-sitter api, Stefan Monnier, 2022/03/31
- RE: [External] : Re: Tree-sitter api, Drew Adams, 2022/03/31
- Re: Tree-sitter api, Filipp Gunbin, 2022/03/31
- Re: Tree-sitter api,
Yuan Fu <=
- Re: Tree-sitter api, Yuan Fu, 2022/03/31
- Re: Tree-sitter api, Yuan Fu, 2022/03/31