From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Albinus <michael.albinus@gmx.de>, emacs-devel@gnu.org
Subject: Re: master 996b9576713 2/3: New function treesit-parser-changed-ranges
Date: Sun, 21 Apr 2024 16:29:15 -0700 [thread overview]
Message-ID: <A3E85229-2D68-4D80-817E-C20BD2696506@gmail.com> (raw)
In-Reply-To: <86il0b8gjb.fsf@gnu.org>
> On Apr 20, 2024, at 9:51 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Yuan Fu <casouri@gmail.com>
>> Date: Sat, 20 Apr 2024 15:32:25 -0700
>> Cc: emacs-devel@gnu.org
>>
>>>> +*** New function 'treesit-parser-changed-ranges' which returns buffer regions that are affected by the last buffer edits
>>>> +
>>>>
>>>> * Changes in Emacs 30.1 on Non-Free Operating Systems
>>>
>>> Achhhh. You still don't respect the line length limit. Please adjust.
>>>
>>> Furthermore, the first line of a NEWS entry must be a sentence of its
>>> own, with a trailing period.
>>>
>>> Best regards, Michael.
>>
>> Sorry about that :-( It should be fixed now.
>
> Did you forget to push?
I forgot to push :-(
>
>> I just realized that you’re talking about the header line, which I always thought are not supposed to be wrapped. I’ll make sure to wrap header lines in the future.
>
> Header lines are indeed not supposed to be wrapped, but they need to
> be shorter than 80 columns. If you cannot say something in that few
> characters, say just part of it and leave the rest to the body of the
> entry. For example, in the above case, I would do it like this:
>
> *** New function 'treesit-parser-changed-ranges'.
> It returns buffer regions that are affected by the last buffer
> edits[…]
I see. It all makes now. Thanks :-)
Yuan
prev parent reply other threads:[~2024-04-21 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171357892097.3235.1021568259110003883@vcs2.savannah.gnu.org>
[not found] ` <20240420020841.F2F5CC1FB68@vcs2.savannah.gnu.org>
2024-04-20 7:19 ` master 996b9576713 2/3: New function treesit-parser-changed-ranges Michael Albinus
2024-04-20 22:32 ` Yuan Fu
2024-04-21 4:51 ` Eli Zaretskii
2024-04-21 23:29 ` Yuan Fu [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=A3E85229-2D68-4D80-817E-C20BD2696506@gmail.com \
--to=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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).