ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

CMake​Format

by jasjuang ST2/ST3

Sublime Plugin for cmake_format (CMake Autoformatter)

Details

Installs

  • Total 1K
  • Win 395
  • OS X 222
  • Linux 515
Jun 25 Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12 Jun 11 Jun 10 Jun 9 Jun 8 Jun 7 Jun 6 Jun 5 Jun 4 Jun 3 Jun 2 Jun 1 May 31 May 30 May 29 May 28 May 27 May 26 May 25 May 24 May 23 May 22 May 21 May 20 May 19 May 18 May 17 May 16 May 15 May 14 May 13 May 12 May 11
Windows 0 0 1 0 0 0 0 0 0 0 0 1 3 0 1 1 1 1 2 1 2 0 0 0 0 0 0 1 1 1 3 1 2 1 1 0 0 0 0 0 1 3 0 0 0 0
OS X 0 0 0 0 0 0 1 0 1 0 0 0 1 0 0 0 0 0 0 1 0 1 1 0 1 1 1 0 1 0 0 0 1 0 1 2 1 0 0 0 0 0 0 1 1 1
Linux 0 0 0 0 2 0 2 2 1 1 0 0 2 1 2 2 0 2 0 1 1 2 1 0 1 0 3 1 1 1 0 1 3 0 0 1 0 0 0 0 2 1 2 1 0 1

Readme

Source
raw.​githubusercontent.​com

Sublime CMake Format

Build Status Package Control

What it does

CMake-format is a tool for formatting CMake files. This is a package that allows you to run it easily from within Sublime Text.

Installing

To install cmake_format, do the following:

  1. Install Python and pip.

  2. Install cmake_format by typing the following in a terminal:

[sudo] pip install cmake_format
  • Please install Sublime CMake and this package through Package Control in the usual way.

  • Set the path to the cmake-format binaries. You can do this from within Sublime Text by choosing CMake Format - Set Path from the command palette. Hint: the path should look something like this /usr/local/bin/cmake-format. If cmake-format is in your system path, you shouldn't need to do anything.

Use

  • Default shortcut is ctrl+shift+c. This will apply cmake-format to the selection.
  • It is possible to run the formatter on every save to a file, change settings to "format_on_save": true.
  • To change settings on a per-package basis, add them under CMakeFormat key, example project.sublime-settings:
{
  "folders": [],
  "settings": {
    "CMakeFormat": {
      "format_on_save": true
    }
  }
}

If You Liked This

  • … And want to contribute, PR's gladly accepted!

Please note that modifications should follow these coding guidelines:

  • Indent is 4 spaces.
  • Code should pass flake8 and pep257 linters.
  • Vertical whitespace helps readability, don’t be afraid to use it.
  • Please use descriptive variable names, no abbreviations unless they are very well known.

Credits

Thanks to cheshirekow for writing cmake format!