C Family Rewrite (as a standalone package)

[camila314]

• [ x ] I'm the package's author and/or maintainer.
• [ x ] I have read the docs.
• [ x ] I have tagged a release with a semver version number.
• [ x ] My package repo has a description and a README describing what it's for and how to use it.
• [ x ] My package doesn't add context menu entries. *
• [ x ] My package doesn't add key bindings. **
• [ x ] Any commands are available via the command palette.
• [ x ] Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
• [ x ] If my package is a syntax it doesn't also add a color scheme. ***
• [ x ] I use .gitattributes to exclude files from the package: images, test files, sublime-project/workspace.

My package is ...

The C Family Rewrite as a standalone package, in all its glory. C, C++, Objective-C, and Objective-C++. Modern, bugs fixed, and with 2023-level features for each language.

[michaelblyons]

LGTM. I hope you will be willing to upstream if/when this matures.

[braver]

Wow, what a project. As someone who's dabbled in syntaxes from time to time I have a lot of respect for the depth of the rewrite. The default packages, and some in the SublimeText org, are of an amazingly high standard. I would never dream of attempting getting close for any language, let alone this set. So, you're looking to let this sit out in the wild for a while to for increased visibility and perhaps someone else might want to contribute?

Just to double check a few things with you that will be hard to change later:

• You're happy with the name of the package? It's long-ish, but fine by me.
• You want to have the description on the entry here, instead of just taking it from the repo? They're different, so I can how you'd want that. But if you remove it here, it will be take from the repo and that way you can change it any time you like.
• If someone were to install this, how would that play out vs the default package? Not sure if there is a lot of inheritance between or dependencies upon the default syntaxes. But the readme could perhaps guide the user a bit in how to have Sublime pick these syntaxes vs any other?