From: Perry Smith <pedz@easesoftware.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Small mistake in Info
Date: Thu, 29 Dec 2022 21:57:50 -0600 [thread overview]
Message-ID: <7832238F-F701-4CE2-A1D5-B81E6AE30930@easesoftware.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
-- Function: treesit-node-type node
Named nodes have “types” (*note node type: tree-sitter node type.).
For example, a named node can be a ‘string_literal’ node, where
‘string_literal’ is its type. The type of an anonymous node is
just the text that the node represents; e.g., the type of a ‘,’
node 480is just ‘,’.
The “480” I assume is not suppose to be there. This is the emacs-29 branch updated today (Dec. 29).
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-12-30 3:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 3:57 Perry Smith [this message]
2022-12-30 4:55 ` Small mistake in Info Yuan Fu
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=7832238F-F701-4CE2-A1D5-B81E6AE30930@easesoftware.com \
--to=pedz@easesoftware.com \
--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).