An open API service indexing awesome lists of open source software.

https://github.com/gingerbill/sublime-cpp11

Sublime C++11
https://github.com/gingerbill/sublime-cpp11

Last synced: 5 months ago
JSON representation

Sublime C++11

Awesome Lists containing this project

README

          

# Sublime C++11

This package provides better support for C and C++11 languages in Sublime Text.

It is primarily focused on improving the default C/C++ syntax highlighting shipped with Sublime Text.

## What is improved?

This color scheme has the ability to allow for custom styling conventions. The default styling convention is this:

* `Types_Are_Like_This` or `TypesAreLikeThis`
* `CONSTANTS_ARE_LIKE_THIS`

It also includes a selection of custom types that are used numerous in projects (i.e. `uint`, `u32`, `i64`, `f32`, `usize`, etc.) and custom keywords (i.e. `gb_internal`, `gb_global`, `gb_local_persist`) for my personal use.

## Installation

### Easy

[Install via Package Control](https://packagecontrol.io/)

### Hard

At a git-enabled command prompt, cd to Sublime Text 3 packages directory:
OS X: ~/Library/Application Support/Sublime Text 3/Packages/User
Windows: %APPDATA%\Sublime Text 3\Packages\User
Linux: ~/.config/sublime-text-3/Packages/User
Install by cloning the repository to your Sublime Text 3 Packages directory:

git clone git://github.com/gingerBill/sublime-cpp11.git

Restart Sublime Text afterwards, switch to C++11 as highlighting profile and try it out with one of the commands above.

## How to customize

You can edit the packages within Sublime using [PackageResourceViewer](https://packagecontrol.io/packages/PackageResourceViewer).

To modify the custom styling, open and edit `C++11.sublime-syntax`.

## Why does this exist?

I, the author ([gingerBill](https://github.com/gingerbill)), created it to aid my development in C and C++ and allow for quick and useful syntax highlighting. I use custom types and keywords that I wanted to have proper syntax highlighting.

The macro highlighting is not perfect but this is not a problem for me personally and these bugs can be _fixed_ by placing a semi-colon on a separate line below the macro.