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

Git​Syntaxes

by vovkkk ST2/ST3

Highlighting for git files in Sublime Text

Details

Installs

  • Total 5K
  • Win 2K
  • OS X 2K
  • Linux 1K
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 May 10
Windows 0 0 1 3 5 1 1 1 1 0 2 2 0 6 0 1 0 0 4 2 0 1 0 2 1 3 1 0 1 1 1 1 2 1 2 0 1 2 1 0 4 1 0 0 0 3
OS X 0 1 0 0 0 0 2 0 0 0 3 0 2 1 2 0 1 0 0 0 0 0 0 1 2 3 3 2 2 0 0 6 0 2 0 0 0 1 2 2 1 1 0 1 2 1
Linux 1 0 1 1 0 0 1 0 0 0 0 3 1 1 0 0 0 0 2 1 0 1 0 0 0 1 0 3 0 0 0 0 2 0 0 2 0 0 0 1 0 2 0 2 2 0

Readme

Source
raw.​githubusercontent.​com

Git Syntaxes

Syntax Highlighting for SublimeText

Features

  • Highlight all Git files (gitconfig, gitattributes, commit message, interactive rebase todo)
  • Toggle comments in all files above with default keystroke whatever it is (usually ctrl + /)
  • Many scopes, e.g. you can set separate colour for every command in rebase file (i.e. pick, fixup, etc.)

Customisation

Sublime Text supports per-syntax settings, for instance, you may want to enable spell check whenever write commit message, or make a font size bigger, or maybe even use completely different colour scheme — all these possible.

Create files:

  1. For commits Packages/User/commit-message.sublime-settings
  2. For rebase Packages/User/rebase.sublime-settings

Content of those files:

{
    "spell_check": true,
    "font_size": 22
}

For available settings look at Preferences → Settings — Default (note, some settings are global and cannot be syntax-specific, e.g. "font_options").

How to use ST as editor for Git

Note for Windows, you must have Build 3065 or later to have command line support, or just add the folder into PATH and call sublime_text instead of subl

  • Mac / Linux: subl -n -w
  • Windows: subl.exe -n -w

Preferred method: edit .bashrc

This will allow for more editing options than just the git commit, like editing diffs. This also leaves flexibility as it can be easily overridden, by the .gitconfig for example. Add the following to your .bashrc: On Mac and Linux:

export EDITOR="subl -n -w"

Alternate method: amend your .gitconfig

You can run the following command to let git update your .gitconfig

git config --global core.editor 'subl -n -w'

Or add the following line manually to your .gitconfig “ [core] editor = 'subl -n -w'

You also can hide menu (as on screenshot above) and tabs:

    editor = "sublime_text -n -w --command toggle_menu --command toggle_tabs"


## SFAQ
### Aren’t there similar packages for those syntaxes? Why another one? Why not contribute into existing one?
I’ve [tried](https://github.com/adambullmer/sublime_git_commit_syntax/pull/1) with no luck, or any feedback.
So this package is an attempt (the first one, in fact) to bring all related syntaxes in one place.

### But what about Git, GitSavvy and many others?
Those packages add integration in an IDE fashion — so you call git from-within Sublime Text.  
This package does an opposite thing — make stuff more readable whenever you call ST from-within git, so ST remains an editor with extra features rather than IDE.

### Are you interested in pull requests or collaboration in general?
Sure, absolutely.

### What is ‘s’ in SFAQ for?
<b>S</b>upposedly frequently asked questions.

### Do you even push-up?
Nope.

## Credits
* Commit definitions are provided by [Josh Goebel](https://github.com/yyyc514)
* Base for Config definitions is borrowed from <https://github.com/textmate/git.tmbundle>

<hr>

All sources under [MIT](LICENSE)