unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Madhu <enometh@meer.net>
To: emacs-devel@gnu.org
Subject: Re: Treesit says grammar is unavailable when it
Date: Fri, 15 Dec 2023 08:13:14 +0530	[thread overview]
Message-ID: <m3edfochj1.fsf@leonis4.robolove.meer.net> (raw)
In-Reply-To: 83r0jpqjd9.fsf@gnu.org

* Eli Zaretskii <83r0jpqjd9.fsf @gnu.org> :
Wrote on Thu, 14 Dec 2023 10:27:30 +0200:
>> > However, I would like to see the patch, since we seem to be
>> > signaling an error already, and the error includes the error
>> > message from dynlib_open?  So what am I missing?

>> We were showing error messages from dlopen, and then removed them for
>> brevity, see e8df6c311fcf59bf23d31b9db2bb8fec9d78fbe7
>
> If these messages are useful, we can revert that commit.
>
>> Maybe we can fold the extra error messages by default?
>
> I'm not sure I understand the details, but the idea is certainly okay.

I still think writing a lisp interface to dlopen and dlclose would iron
out a lot of things in the details and make it useful for treesitter
related stuff.  Or is the locking down the ffi interface done for FSF
reasons?

On another note, I also went through the same process with yaml-ts-mode,
A pointer to where the treesitter plugin is available is missing from
the docs.  Then one has to turn to third parties for this information
and to find the providers and toolchain providers and do the dance to
their tunes.

But most disappointing thing was that the modes come with absolutely no
navigation functions. These are structured files, and emacs has provides
way to navigate the structures.  This is a general quality defect from
to "prog" abstractions.  (when the facililties are provided they are
inadequate and a dedicated mode would have taken the diligence to do it
right)




  reply	other threads:[~2023-12-15  2:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 12:43 Treesit says grammar is unavailable when it Gernot Kieseritzky
2023-12-13  3:33 ` Yuan Fu
2023-12-13 12:00   ` Eli Zaretskii
2023-12-14  8:14     ` Yuan Fu
2023-12-14  8:27       ` Eli Zaretskii
2023-12-15  2:43         ` Madhu [this message]
2023-12-15  9:00           ` Eli Zaretskii
2023-12-17  6:31         ` Yuan Fu
2023-12-17  8:32           ` Eli Zaretskii
2023-12-27  6:41             ` Yuan Fu
  -- strict thread matches above, loose matches on Subject: below --
2023-03-10  9:24 mprodrigues
2023-03-10 12:32 ` 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=m3edfochj1.fsf@leonis4.robolove.meer.net \
    --to=enometh@meer.net \
    --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).