unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Yuan Fu <casouri@gmail.com>,
	60256-done@debbugs.gnu.org, wilhelm@floatpays.co.za
Subject: bug#60256: 29.0.60; Maybe improve tree sitter default treesit-language-at function
Date: Sat, 2 Sep 2023 09:41:05 -0700	[thread overview]
Message-ID: <CADwFkm=nDGzXTGfajeayXhO4C72GnZr2i-CeiZvwBDUFfjY1Ag@mail.gmail.com> (raw)
In-Reply-To: <83h6xk3s0s.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 25 Dec 2022 08:40:35 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> tags 60256 wontfix
> thanks
>
>> From: Yuan Fu <casouri@gmail.com>
>> Date: Sat, 24 Dec 2022 14:43:18 -0800
>> Cc: Wilhelm Hugo Kirschbaum <wilhelm@floatpays.co.za>,
>>  60256@debbugs.gnu.org
>>
>>
>> Yeah, sorry for the delay. I don’t think it’s worth it, because (1) I
>> expect major modes with multiple langauges to implement
>> treesit-language-at-point-function which takes care of all the work, and
>> (2) in the rare case where there are multiple languages and no
>> treesit-language-at-point-function, using the first language whose range
>> spans point (this patch) is not necessarily correct: the host language (eg, HTML
>> among HTML, CSS & JavaScript) always covers the whole buffer, only
>> embedded languages has ranges.
>
> OK, thanks.

I'm therefore closing this bug report.





      reply	other threads:[~2023-09-02 16:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 10:30 bug#60256: 29.0.60; Maybe improve tree sitter default treesit-language-at function Wilhelm H Kirschbaum
2022-12-24  7:25 ` Eli Zaretskii
2022-12-24 22:43 ` Yuan Fu
2022-12-25  6:40   ` Eli Zaretskii
2023-09-02 16:41     ` Stefan Kangas [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='CADwFkm=nDGzXTGfajeayXhO4C72GnZr2i-CeiZvwBDUFfjY1Ag@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=60256-done@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=eliz@gnu.org \
    --cc=wilhelm@floatpays.co.za \
    /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).