all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: 60555@debbugs.gnu.org
Subject: bug#60555: 29.0.50; Some clarification is needed about "smaller" and "larger" Tree-sitter nodes
Date: Thu, 05 Jan 2023 08:24:07 +0200	[thread overview]
Message-ID: <83lemhxzw8.fsf@gnu.org> (raw)
In-Reply-To: <m1bknd3np4.fsf@yahoo.es> (message from Daniel Martín on Thu, 05 Jan 2023 00:05:43 +0100)

> From: Daniel Martín <mardani29@yahoo.es>
> Cc: 60555@debbugs.gnu.org
> Date: Thu, 05 Jan 2023 00:05:43 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > They aren't orthogonal, AFAIU.  The text actually says that "lower"
> > necessarily also means "smaller".
> 
> If that's the case, I don't feel the text is clear enough about the
> "necessarily" part. I think the text would be more clear if the first
> sentence was
> 
>   We talk about a node being “smaller” (or "lower") and “larger” (or
>   “higher”).

Adding parentheses makes the text harder to read, IME.  You kept all
the words and the sentence structure, so everything else is unchanged,
and the added complexity isn't justified, IMO.

> The next sentence should avoid "smaller and lower" and "larger and
> higher", because it'd be redundant (can a node be "smaller and
> higher"?).  That is, I suggest the following text instead:
> 
>   A smaller node is lower in the syntax tree and therefore spans a
> smaller portion of buffer text; a larger 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 these micro-changes are basically splitting hair, and the text
you propose will almost certainly be less clear for someone.  If the
original text is unclear, the way to fix that is to rewrite it in a
completely different way.  If you try explaining what exactly confuses
you, maybe I could come up with such a rewrite.  I cannot myself
understand what's unclear, because to me it sounds very clear and
simple to understand.  So I need your help.  Try to recollect what
confused you when you first read this.





  reply	other threads:[~2023-01-05  6:24 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 ` bug#60555: 29.0.50; Some clarification is needed about "smaller" and "larger" Tree-sitter nodes Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-04 14:58   ` 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 [this message]
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

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

  git send-email \
    --in-reply-to=83lemhxzw8.fsf@gnu.org \
    --to=eliz@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 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.