all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mohammed Sadiq <sadiq@sadiqpk.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60484@debbugs.gnu.org
Subject: bug#60484: 29.0.60; c-ts-mode: short tokens are not identified as type_identifier
Date: Mon, 02 Jan 2023 18:13:34 +0530	[thread overview]
Message-ID: <1d2f9bd1c64ed11124a0129b0ae8b672@sadiqpk.org> (raw)
In-Reply-To: <83358t2kv1.fsf@gnu.org>

On 2023-01-02 17:45, Eli Zaretskii wrote:
>> Date: Mon, 02 Jan 2023 10:22:09 +0530
>> From: Mohammed Sadiq <sadiq@sadiqpk.org>
>> 
>> Short tokens are not identified as type_identifier in GNU Emacs
>> c-ts-mode, but does work fine with tree-sitter playground[0].
>> 
>> Say for example, 'a_type' in an empty buffer is identified as a
>> type_identifier in tree-sitter playground, but not in c-ts-mode,
>> while say, some longer tokens like 'window_type' is identified as
>> type_identifier.
> 
> Where is it written that FOO_type is a type identifier?  is this
> something new in some recent C Standard?  Or is it just a popular
> convention?

'a_type' was just a made up example, it can be any valid token, say
'g_file', or whatever.  I was pointing out a disparity in handling of
some token in c-ts-mode and tree-sitter: tree-sitter identifiers a 6
byte length token as an identifier, but c-ts-mode requires it to be
at least 11 byte sized for custom types.





  reply	other threads:[~2023-01-02 12:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-02  4:52 bug#60484: 29.0.60; c-ts-mode: short tokens are not identified as type_identifier Mohammed Sadiq
2023-01-02 12:15 ` Eli Zaretskii
2023-01-02 12:43   ` Mohammed Sadiq [this message]
2023-01-02 12:45     ` Eli Zaretskii
2023-01-02 13:20       ` Mohammed Sadiq
2023-01-02 22:41 ` Yuan Fu
2023-01-08  0:57 ` 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

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

  git send-email \
    --in-reply-to=1d2f9bd1c64ed11124a0129b0ae8b672@sadiqpk.org \
    --to=sadiq@sadiqpk.org \
    --cc=60484@debbugs.gnu.org \
    --cc=eliz@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 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.