all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: Theodor Thornhill <theo@thornhill.no>
Cc: 59627-done@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#59627: 29.0.50; tree-sitter support not documented in emacs  manual
Date: Sat, 7 Jan 2023 15:00:19 -0800	[thread overview]
Message-ID: <05A471E5-2793-4464-B97A-3B1023508ECC@gmail.com> (raw)
In-Reply-To: <CADwFkmnFLc5YaAyEyrP6F60J_uCqCT9Ht20k8RvN4g-EymF0XA@mail.gmail.com>


Yuan Fu <casouri@gmail.com> writes:

>> On Nov 27, 2022, at 3:41 AM, Theodor Thornhill <theo@thornhill.no> wrote:
>> 
>> Stefan Kangas <stefankangas@gmail.com> writes:
>> 
>>> The new tree-sitter support is not documented in the emacs manual, only
>>> in the elisp one.  Should it be?
>> 
>> To me it seems like the Emacs manual covers broader strokes and
>> concepts, while tree-sitter still is "just" an internal implementation
>> detail.  I'm not sure exactly where this distinction goes, though.
>> 
>> Theo
>
> I think the plans is to add a section in the Emacs manual. There are
> some functions and variables intended to be included in the Emacs
> manual that I left out of the Elisp manual. The Emacs manual should
> also explain font-lock features.

I think there is not need to keep this open as an reminder. IIUC Eli is
working on the Emacs manual. So I’m closing this.

Yuan





      parent reply	other threads:[~2023-01-07 23:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27  9:38 bug#59627: 29.0.50; tree-sitter support not documented in emacs manual Stefan Kangas
2022-11-27 11:41 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-27 22:27   ` Yuan Fu
2023-01-07 23:00 ` Yuan Fu [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=05A471E5-2793-4464-B97A-3B1023508ECC@gmail.com \
    --to=casouri@gmail.com \
    --cc=59627-done@debbugs.gnu.org \
    --cc=stefankangas@gmail.com \
    --cc=theo@thornhill.no \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.