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: Sat, 07 Jan 2023 11:26:57 +0200 [thread overview]
Message-ID: <838rieu23i.fsf@gnu.org> (raw)
In-Reply-To: <m1cz7t1fjc.fsf@yahoo.es> (message from Daniel Martín on Thu, 05 Jan 2023 10:44:55 +0100)
> From: Daniel Martín <mardani29@yahoo.es>
> Cc: 60555@debbugs.gnu.org
> Date: Thu, 05 Jan 2023 10:44:55 +0100
>
> >
> > 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.
>
> My main confusion happened after reading this sentence:
>
> We talk about a node being “smaller” or “larger”, and “lower” or
> “higher”.
>
> That made me think there are two different dimensions we classify nodes:
> "Size", that is, if the node is small or large, and "height", that is,
> if it is low or high. I was hoping to learn the differences between
> "size" and "height" in the rest of the text, but the text didn't make it
> clear to me because it only talks about "smaller and lower" and "larger
> and higher". What about "smaller and higher", or "larger and lower"?
> Are they possible at all? After reading everything, I got the idea that
> the terms may actually be synonyms, but I was not 100% sure. I feel we
> could make this more clear from the start.
>
> All of this is my perspective as a non-native English speaker. Hope
> this helps.
Thanks, I've now reworded that text, please take a look.
next prev parent reply other threads:[~2023-01-07 9:26 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
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 [this message]
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=838rieu23i.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.