unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 60555@debbugs.gnu.org
Subject: bug#60555: 29.0.50; Some clarification is needed about "smaller" and "larger" Tree-sitter nodes
Date: Wed, 04 Jan 2023 15:29:14 +0100	[thread overview]
Message-ID: <m1y1qibcg5.fsf@yahoo.es> (raw)
In-Reply-To: m1y1qibcg5.fsf.ref@yahoo.es


In the Elisp manual, under "37.3 Retrieving Nodes" there is this text:

   We talk about a node being “smaller” or “larger”, and “lower” or
“higher”.  A smaller and lower node is lower in the syntax tree and
therefore spans a smaller portion of buffer text; a larger and higher
node is higher up in the syntax tree, it contains many smaller nodes as
its children, and therefore spans a larger portion of text.

I think the concepts of nodes being "lower" and "higher" are more or
less clear, and the notation is similar to the one used in classic texts
about rooted trees.  However, the concepts of "smaller" and "larger" are
not very clear to me.  From the text, it seems that "lower" also means
"smaller", and "higher" always means "larger".  Is that correct, or
"smaller" and "larger" are really orthogonal to "lower" and "higher"?
If that's the case, I think the text needs some clarification, ideally
with a brief example.

Thanks.





       reply	other threads:[~2023-01-04 14:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m1y1qibcg5.fsf.ref@yahoo.es>
2023-01-04 14:29 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-01-04 14:58   ` bug#60555: 29.0.50; Some clarification is needed about "smaller" and "larger" Tree-sitter nodes Eli Zaretskii
2023-01-04 23:05     ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-05  6:24       ` Eli Zaretskii
2023-01-05  9:44         ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-07  9:26           ` Eli Zaretskii
2023-01-07 11:38             ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=m1y1qibcg5.fsf@yahoo.es \
    --to=bug-gnu-emacs@gnu.org \
    --cc=60555@debbugs.gnu.org \
    --cc=mardani29@yahoo.es \
    /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).