From: Po Lu <luangruo@yahoo.com>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: master c916f471caa 2/3: Add tree-sitter performance note
Date: Thu, 14 Sep 2023 12:18:37 +0800 [thread overview]
Message-ID: <s0d1qf11j6q.fsf@yahoo.com> (raw)
In-Reply-To: <5F1D1C9B-1CF3-4F77-BE30-605B23D89577@gmail.com> (Yuan Fu's message of "Wed, 13 Sep 2023 21:08:37 -0700")
Yuan Fu <casouri@gmail.com> writes:
> Indeed it should. Thanks for catching this. I use word-wrap so filled
> and unfilled paragraph look the same to me, apparently I forgot to
> fill this paragraph.
OK, thanks. I truncate long lines :-)
prev parent reply other threads:[~2023-09-14 4:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169465413983.20865.4955758569389021990@vcs2.savannah.gnu.org>
[not found] ` <20230914011540.707B4C04DAF@vcs2.savannah.gnu.org>
2023-09-14 1:43 ` master c916f471caa 2/3: Add tree-sitter performance note Po Lu
2023-09-14 4:08 ` Yuan Fu
2023-09-14 4:18 ` Po Lu [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
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=s0d1qf11j6q.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=casouri@gmail.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).