From: Po Lu via "Emacs development discussions." <emacs-devel@gnu.org>
To: emacs-devel@gnu.org
Cc: Yuan Fu <casouri@gmail.com>
Subject: Re: emacs-30 bed38ded730: ; * src/treesit.c (treesit_debug_print_parser_list): Fix formatting.
Date: Mon, 09 Sep 2024 13:38:43 +0800 [thread overview]
Message-ID: <s1rjzflbd3w.fsf@yahoo.com> (raw)
In-Reply-To: <20240909041443.4DAE4C41F20@vcs2.savannah.gnu.org> (Yuan Fu's message of "Mon, 9 Sep 2024 00:14:43 -0400 (EDT)")
Yuan Fu <casouri@gmail.com> writes:
> branch: emacs-30
> commit bed38ded730130d63f08af7ad4049d87efe9bcf8
> Author: Yuan Fu <casouri@gmail.com>
> Commit: Yuan Fu <casouri@gmail.com>
>
> ; * src/treesit.c (treesit_debug_print_parser_list): Fix formatting.
> ---
> src/treesit.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/src/treesit.c b/src/treesit.c
> index 0effb5d13b5..d1c50771e23 100644
> --- a/src/treesit.c
> +++ b/src/treesit.c
> @@ -487,8 +487,11 @@ treesit_initialize (void)
> \f
> /*** Debugging */
>
> -void treesit_debug_print_parser_list (char *, Lisp_Object);
> -void treesit_debug_print_parser_list (char *msg, Lisp_Object parser)
> +void
> +treesit_debug_print_parser_list (char *, Lisp_Object);
Such newlines should only be inserted in definitions, not mere
declarations.
> +void
> +treesit_debug_print_parser_list (char *msg, Lisp_Object parser)
> {
> struct buffer *buf = XBUFFER (XTS_PARSER (parser)->buffer);
> char *buf_name = SSDATA (BVAR (buf, name));
next parent reply other threads:[~2024-09-09 5:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <172585528292.11654.14274626449222552967@vcs2.savannah.gnu.org>
[not found] ` <20240909041443.4DAE4C41F20@vcs2.savannah.gnu.org>
2024-09-09 5:38 ` Po Lu via Emacs development discussions. [this message]
2024-09-09 7:05 ` emacs-30 bed38ded730: ; * src/treesit.c (treesit_debug_print_parser_list): Fix formatting Yuan Fu
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=s1rjzflbd3w.fsf@yahoo.com \
--to=emacs-devel@gnu.org \
--cc=casouri@gmail.com \
--cc=luangruo@yahoo.com \
/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).